@taazkareem/clickup-mcp-server 0.6.4 → 0.6.5

package/README.md

@@ -6,7 +6,7 @@
 
 A Model Context Protocol (MCP) server for integrating ClickUp tasks with AI applications. This server allows AI agents to interact with ClickUp tasks, spaces, lists, and folders through a standardized protocol.
 
-> 🚧 **Status Update:** Rolling out v0.6.3 will add Global Task Lookup with smart disambiguation, Start Date Support for tasks with natural language expressions, Complete Tag Support including natural language tag color commands, Subtasks Support, Custom ID Support, and Logging Fixes
+> 🚧 **Status Update:** Rolling out v0.6.4 will add Global Task Lookup with smart disambiguation, Start Date Support for tasks with natural language expressions, Complete Tag Support including natural language tag color commands, Subtasks Support, Custom ID Support, and Logging Fixes
 
 ## Setup
 

package/build/config.js

@@ -43,7 +43,7 @@ export const parseLogLevel = (levelStr) => {
         case 'WARN': return LogLevel.WARN;
         case 'ERROR': return LogLevel.ERROR;
         default:
-            console.error(`Invalid LOG_LEVEL: ${levelStr}, defaulting to ERROR`);
+            // Don't use console.error as it interferes with JSON-RPC communication
             return LogLevel.ERROR;
     }
 };
@@ -54,8 +54,7 @@ const configuration = {
     enableSponsorMessage: process.env.ENABLE_SPONSOR_MESSAGE !== 'false',
     logLevel: parseLogLevel(envArgs.logLevel || process.env.LOG_LEVEL)
 };
-// Log the configured log level (but only to console to avoid circular dependency)
-console.debug(`Log level set to: ${LogLevel[configuration.logLevel]}`);
+// Don't log to console as it interferes with JSON-RPC communication
 // Validate only the required variables are present
 const requiredVars = ['clickupApiKey', 'clickupTeamId'];
 const missingEnvVars = requiredVars

package/build/index.js

@@ -23,43 +23,27 @@
  */
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { configureServer, server } from "./server.js";
-import { info, error, warn } from "./logger.js";
-import { exec } from 'child_process';
-import { promisify } from 'util';
-const execAsync = promisify(exec);
-/**
- * Check if another instance of the server is already running
- * @returns Boolean indicating if this is the only instance
- */
-async function checkSingleInstance() {
-    try {
-        const { stdout } = await execAsync(`ps aux | grep "node.*clickup-mcp-server" | grep -v grep | wc -l`);
-        const instanceCount = parseInt(stdout.trim(), 10);
-        // If there's more than one instance (including this one), warn and exit
-        if (instanceCount > 1) {
-            error(`Multiple server instances detected (${instanceCount}). This may cause issues.`);
-            info("Use 'pkill -9 -f clickup-mcp-server' to kill all instances before starting a new one.");
-            return false;
-        }
-        return true;
-    }
-    catch (err) {
-        error("Failed to check for other running instances", err);
-        // Continue execution even if check fails
-        return true;
-    }
-}
+import { info, error } from "./logger.js";
+import { dirname } from 'path';
+import { fileURLToPath } from 'url';
+// Get directory name for module paths
+const __dirname = dirname(fileURLToPath(import.meta.url));
+// Handle uncaught exceptions
+process.on('uncaughtException', (err) => {
+    error("Uncaught Exception", { message: err.message, stack: err.stack });
+    process.exit(1);
+});
+// Handle unhandled promise rejections
+process.on('unhandledRejection', (reason, promise) => {
+    error("Unhandled Rejection", { reason });
+    process.exit(1);
+});
 /**
  * Application entry point that configures and starts the MCP server.
  */
 async function main() {
     try {
         info("Starting ClickUp MCP Server...");
-        // Check if we're the only instance
-        const isSingleInstance = await checkSingleInstance();
-        if (!isSingleInstance) {
-            warn("Continuing startup despite multiple instances detected");
-        }
         // Log essential information about the environment
         info("Server environment", {
             pid: process.pid,
@@ -77,11 +61,11 @@ async function main() {
         info("Server startup complete - ready to handle requests");
     }
     catch (err) {
-        error("Error during server startup", err);
+        error("Error during server startup", { message: err.message, stack: err.stack });
         process.exit(1);
     }
 }
 main().catch((err) => {
-    error("Unhandled server error", err);
+    error("Unhandled server error", { message: err.message, stack: err.stack });
     process.exit(1);
 });

package/build/logger.js

@@ -5,7 +5,7 @@
  * Logger module for MCP Server
  *
  * This module provides logging functionality for the server,
- * writing logs to both the console and a log file in the build folder.
+ * writing logs to only the log file to avoid interfering with JSON-RPC.
  */
 import { createWriteStream } from 'fs';
 import { join, dirname } from 'path';
@@ -18,7 +18,8 @@ const pid = process.pid;
 // Create a write stream for logging - use a fixed filename in the build directory
 const logFileName = 'server.log';
 const logStream = createWriteStream(join(__dirname, logFileName), { flags: 'w' });
-console.error(`Logging to ${join(__dirname, logFileName)}`);
+// Write init message to log file only
+logStream.write(`Logging initialized to ${join(__dirname, logFileName)}\n`);
 // Use the configured log level from config.ts
 const configuredLevel = config.logLevel;
 // Re-export LogLevel enum
@@ -32,7 +33,7 @@ export function isLevelEnabled(level) {
     return level >= configuredLevel;
 }
 /**
- * Log function that writes to both console and file
+ * Log function that writes only to file to avoid interfering with JSON-RPC
  * @param level Log level (trace, debug, info, warn, error)
  * @param message Message to log
  * @param data Optional data to include in log
@@ -74,9 +75,7 @@ export function log(level, message, data) {
             logMessage += '\n' + JSON.stringify(data, null, 2);
         }
     }
-    // When using stdio transport, log to stderr which is captured by host application
-    console.error(logMessage);
-    // Write to file
+    // Write to file only, not to stderr which would interfere with JSON-RPC
     logStream.write(logMessage + '\n');
 }
 /**

package/build/server.js

@@ -5,12 +5,12 @@
  * MCP Server for ClickUp integration
  */
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
-import { CallToolRequestSchema, ListToolsRequestSchema, ListPromptsRequestSchema, GetPromptRequestSchema, } from "@modelcontextprotocol/sdk/types.js";
+import { CallToolRequestSchema, ListToolsRequestSchema, ListPromptsRequestSchema, GetPromptRequestSchema, ListResourcesRequestSchema, } from "@modelcontextprotocol/sdk/types.js";
 import { workspaceHierarchyTool, handleGetWorkspaceHierarchy } from "./tools/workspace.js";
 import { createTaskTool, updateTaskTool, moveTaskTool, duplicateTaskTool, getTaskTool, getTasksTool, deleteTaskTool, getTaskCommentsTool, createTaskCommentTool, createBulkTasksTool, updateBulkTasksTool, moveBulkTasksTool, deleteBulkTasksTool, attachTaskFileTool, getWorkspaceTasksTool, handleCreateTask, handleUpdateTask, handleMoveTask, handleDuplicateTask, handleGetTasks, handleDeleteTask, handleGetTaskComments, handleCreateTaskComment, handleCreateBulkTasks, handleUpdateBulkTasks, handleMoveBulkTasks, handleDeleteBulkTasks, handleGetTask, handleAttachTaskFile, handleGetWorkspaceTasks } from "./tools/task/index.js";
 import { createListTool, handleCreateList, createListInFolderTool, handleCreateListInFolder, getListTool, handleGetList, updateListTool, handleUpdateList, deleteListTool, handleDeleteList } from "./tools/list.js";
 import { createFolderTool, handleCreateFolder, getFolderTool, handleGetFolder, updateFolderTool, handleUpdateFolder, deleteFolderTool, handleDeleteFolder } from "./tools/folder.js";
-import { getSpaceTagsTool, handleGetSpaceTags, createSpaceTagTool, handleCreateSpaceTag, updateSpaceTagTool, handleUpdateSpaceTag, deleteSpaceTagTool, handleDeleteSpaceTag, addTagToTaskTool, handleAddTagToTask, removeTagFromTaskTool, handleRemoveTagFromTask } from "./tools/tag.js";
+import { getSpaceTagsTool, handleGetSpaceTags, addTagToTaskTool, handleAddTagToTask, removeTagFromTaskTool, handleRemoveTagFromTask } from "./tools/tag.js";
 import { Logger } from "./logger.js";
 import { clickUpServices } from "./services/shared.js";
 // Create a logger instance for server
@@ -19,11 +19,12 @@ const logger = new Logger('Server');
 const { workspace } = clickUpServices;
 export const server = new Server({
     name: "clickup-mcp-server",
-    version: "0.6.4",
+    version: "0.6.5",
 }, {
     capabilities: {
         tools: {},
         prompts: {},
+        resources: {},
     },
 });
 /**
@@ -62,17 +63,19 @@ export function configureServer() {
                 updateFolderTool,
                 deleteFolderTool,
                 getSpaceTagsTool,
-                createSpaceTagTool,
-                updateSpaceTagTool,
-                deleteSpaceTagTool,
                 addTagToTaskTool,
                 removeTagFromTaskTool
             ]
         };
     });
+    // Add handler for resources/list
+    server.setRequestHandler(ListResourcesRequestSchema, async (req) => {
+        logger.debug("Received ListResources request");
+        return { resources: [] };
+    });
     // Register CallTool handler with proper logging
     logger.info("Registering tool handlers", {
-        toolCount: 31,
+        toolCount: 28,
         categories: ["workspace", "task", "list", "folder", "tag"]
     });
     server.setRequestHandler(CallToolRequestSchema, async (req) => {
@@ -136,24 +139,39 @@ export function configureServer() {
                     return handleDeleteFolder(params);
                 case "get_space_tags":
                     return handleGetSpaceTags(params);
-                case "create_space_tag":
-                    return handleCreateSpaceTag(params);
-                case "update_space_tag":
-                    return handleUpdateSpaceTag(params);
-                case "delete_space_tag":
-                    return handleDeleteSpaceTag(params);
                 case "add_tag_to_task":
                     return handleAddTagToTask(params);
                 case "remove_tag_from_task":
                     return handleRemoveTagFromTask(params);
                 default:
                     logger.error(`Unknown tool requested: ${name}`);
-                    throw new Error(`Unknown tool: ${name}`);
+                    const error = new Error(`Unknown tool: ${name}`);
+                    error.name = "UnknownToolError";
+                    throw error;
             }
         }
         catch (err) {
             logger.error(`Error executing tool: ${name}`, err);
-            throw err;
+            // Transform error to a more descriptive JSON-RPC error
+            if (err.name === "UnknownToolError") {
+                throw {
+                    code: -32601,
+                    message: `Method not found: ${name}`
+                };
+            }
+            else if (err.name === "ValidationError") {
+                throw {
+                    code: -32602,
+                    message: `Invalid params for tool ${name}: ${err.message}`
+                };
+            }
+            else {
+                // Generic server error
+                throw {
+                    code: -32000,
+                    message: `Error executing tool ${name}: ${err.message}`
+                };
+            }
         }
     });
     server.setRequestHandler(ListPromptsRequestSchema, async () => {

package/build/tools/tag.js

@@ -26,15 +26,11 @@ export const getSpaceTagsTool = {
     description: `Purpose: Get all tags available in a ClickUp space.
 
 Valid Usage:
-1. Provide spaceId (preferred if available)
-2. Provide spaceName (will be resolved to a space ID)
+1. Provide spaceId (preferred)
+2. Provide spaceName
 
 Requirements:
-- EITHER spaceId OR spaceName is REQUIRED
-
-Notes:
-- Tags are defined at the space level in ClickUp
-- You need to know the available tags before adding them to tasks`,
+- Space identification: EITHER spaceId OR spaceName REQUIRED`,
     inputSchema: {
         type: "object",
         properties: {
@@ -57,18 +53,15 @@ export const createSpaceTagTool = {
     description: `Purpose: Create a new tag in a ClickUp space.
 
 Valid Usage:
-1. Provide spaceId (preferred if available)
-2. Provide spaceName (will be resolved to a space ID)
+1. Provide spaceId + tagName (preferred)
+2. Provide spaceName + tagName
 
 Requirements:
 - tagName: REQUIRED
-- EITHER spaceId OR spaceName: REQUIRED
+- Space identification: EITHER spaceId OR spaceName REQUIRED
 
 Notes:
-- New tag will be available for all tasks in the space
-- You can specify background and foreground colors in HEX format (e.g., #FF0000)
-- You can also provide a color command (e.g., "blue tag") to automatically generate colors
-- After creating a tag, you can add it to tasks using add_tag_to_task`,
+- Specify colors with HEX values or natural language command`,
     inputSchema: {
         type: "object",
         properties: {

package/build/tools/task/attachments.js

@@ -33,39 +33,23 @@ export const attachTaskFileTool = {
     description: `Purpose: Attaches a file to a ClickUp task.
 
 Valid Usage:
-1. Use taskId alone (preferred) - works with both regular and custom IDs
-2. Use taskName alone (will search across all lists)
-3. Use taskName + listName (for faster, targeted search)
+1. Use taskId (preferred) - works with both regular and custom IDs
+2. Use taskName + listName for targeted search
 
-File Source Options:
-1. Upload from base64: Provide file_data + file_name
-2. Upload from URL: Provide file_url starting with http:// or https://
-3. Upload from local file: Provide file_url as absolute path (starting with / or drive letter)
-4. For large files: Use chunk_* parameters for advanced chunked uploading
+File Sources:
+- Base64: Provide file_data + file_name
+- URL: Provide file_url starting with http:// or https://
+- Local file: Provide file_url as absolute path
+- Chunked upload: Use chunk_* parameters for large files
 
 Requirements:
-- EITHER taskId OR taskName: REQUIRED
-- listName: Optional, but recommended when using taskName
-- File Source: ONE of the following is REQUIRED:
-  - file_data + file_name
-  - file_url (web URL or local path)
-  - chunk_session (for continuing chunked upload)
+- Task identification: EITHER taskId OR taskName REQUIRED
+- File source: EITHER file_data+file_name OR file_url OR chunk_session REQUIRED
 
 Notes:
-- The tool automatically searches for tasks using smart name matching
-- When only taskName is provided, it searches across all lists
-- Adding listName narrows the search to a specific list for better performance
-- The system automatically selects the best upload method based on file size and source:
-  - Base64 method: Limited to 10MB due to encoding overhead
-  - URL method: Works for files hosted online
-  - Local file method: Works with absolute paths only
-  - Large files: Automatically uses chunked uploading
-
-Warning:
-- Using taskName without listName may match multiple tasks
-- If multiple matches are found, the operation will fail with a disambiguation error
-- For local files, relative paths are not supported
-- Base64 uploads over 10MB will automatically switch to chunked upload mode`,
+- System automatically selects best upload method based on file size
+- Base64 uploads limited to 10MB
+- Using taskName without listName may match multiple tasks`,
     inputSchema: {
         type: "object",
         properties: {

package/build/tools/task/bulk-operations.js

@@ -81,13 +81,11 @@ Valid Usage:
 
 Requirements:
 - tasks: REQUIRED (array of tasks, each with at least a name)
-- EITHER listId OR listName: REQUIRED
-- All tasks will be created in the specified list
+- List identification: EITHER listId OR listName REQUIRED
 
 Notes:
-- Configure batch size and concurrency via options for performance
-- Each task should have a name with emoji prefix
-- Custom fields can be set for each task using the custom_fields property (array of {id, value} objects)`,
+- Configure batch processing via options parameter
+- Custom fields supported for each task`,
     inputSchema: {
         type: "object",
         properties: {
@@ -170,22 +168,16 @@ export const updateBulkTasksTool = {
     description: `Purpose: Update multiple tasks efficiently in a single operation.
 
 Valid Usage:
-1. For each task, provide taskId (preferred)
-2. For each task, provide taskName + listName
+1. Provide array of tasks with taskId (preferred)
+2. Provide array of tasks with taskName + listName
 
 Requirements:
 - tasks: REQUIRED (array of tasks to update)
-- For each task entry, EITHER taskId OR (taskName + listName) is REQUIRED
-- At least one update field per task (name, description, status, priority, dueDate)
+- Each task needs identification and update fields
 
 Notes:
 - Only specified fields will be updated for each task
-- Configure batch size and concurrency via options for performance
-- Each task can have different fields to update
-- Custom fields can be updated using the custom_fields property (array of {id, value} objects)
-
-Warning:
-- Using taskName without listName will fail as tasks may have identical names across lists`,
+- Configure batch processing via options parameter`,
     inputSchema: {
         type: "object",
         properties: {
@@ -269,21 +261,14 @@ export const moveBulkTasksTool = {
     description: `Purpose: Move multiple tasks to a different list efficiently.
 
 Valid Usage:
-1. For each task, provide taskId + target list (preferred)
-2. For each task, provide taskName + listName + target list
+1. Provide tasks array + target list
 
 Requirements:
-- tasks: REQUIRED (array of tasks to move)
-- EITHER targetListId OR targetListName: REQUIRED
-- For each task entry, EITHER taskId OR (taskName + listName) is REQUIRED
-
-Notes:
-- Configure batch size and concurrency via options for performance
-- All tasks will be moved to the same destination list
+- tasks: REQUIRED (array of task identifiers)
+- Target list: EITHER targetListId OR targetListName REQUIRED
 
 Warning:
-- Task statuses may reset if destination list has different status options
-- Using taskName without listName will fail as tasks may have identical names across lists`,
+- Task statuses may reset if destination list has different status options`,
     inputSchema: {
         type: "object",
         properties: {
@@ -333,20 +318,15 @@ export const deleteBulkTasksTool = {
     description: `Purpose: PERMANENTLY DELETE multiple tasks at once.
 
 Valid Usage:
-1. For each task, provide taskId (preferred and safest)
-2. For each task, provide taskName + listName
+1. Provide array of tasks with taskId (preferred)
+2. Provide array of tasks with taskName + listName
 
 Requirements:
-- tasks: REQUIRED (array of tasks to delete)
-- For each task entry, EITHER taskId OR (taskName + listName) is REQUIRED
-
-Notes:
-- Configure batch size and concurrency via options for performance
+- tasks: REQUIRED (array of task identifiers)
 
 Warning:
-- This action CANNOT be undone for any of the tasks
-- Using taskName without listName is dangerous as names may not be unique
-- Always provide listName when using taskName for safer targeting`,
+- This action CANNOT be undone
+- Always provide listName when using taskName`,
     inputSchema: {
         type: "object",
         properties: {

package/build/tools/task/single-operations.js

@@ -52,17 +52,16 @@ export const createTaskTool = {
 
 Valid Usage:
 1. Provide listId (preferred if available)
-2. Provide listName (system will look up the list ID)
+2. Provide listName (will look up the list ID)
 
 Requirements:
 - name: REQUIRED
-- EITHER listId OR listName: REQUIRED
+- List identification: EITHER listId OR listName REQUIRED
 
 Notes:
-- For multiple tasks, use create_bulk_tasks instead
-- Reuse list IDs from previous responses when possible to avoid redundant lookups
-- To create a subtask, set the parent parameter to the ID of the parent task
-- Custom fields can be set using the custom_fields parameter (array of {id, value} objects)`,
+- Use create_bulk_tasks for multiple tasks
+- Set parent parameter to create a subtask
+- Custom fields can be set via custom_fields parameter`,
     inputSchema: {
         type: "object",
         properties: {
@@ -145,25 +144,17 @@ export const updateTaskTool = {
     description: `Purpose: Modify properties of an existing task.
 
 Valid Usage:
-1. Use taskId alone (preferred) - works with both regular and custom IDs
-2. Use taskName alone (will search across all lists)
-3. Use taskName + listName (for faster, targeted search)
+1. Use taskId (preferred) - works with both regular and custom IDs
+2. Use taskName + listName for targeted search
 
 Requirements:
-- At least one update field (name, description, status, priority, dueDate) must be provided
-- EITHER taskId OR taskName: REQUIRED
-- listName: Optional, but recommended when using taskName
+- Task identification: EITHER taskId OR taskName REQUIRED
+- Updates: At least one update field (name, description, status, priority, dueDate) REQUIRED
 
 Notes:
-- The tool automatically searches for tasks using smart name matching
-- When only taskName is provided, it searches across all lists
-- Adding listName narrows the search to a specific list for better performance
 - Only specified fields will be updated
-- Custom fields can be set using the custom_fields parameter (array of {id, value} objects)
-
-Warning:
-- Using taskName without listName may match multiple tasks
-- If multiple matches are found, the operation will fail with a disambiguation error`,
+- Custom fields can be set using the custom_fields parameter
+- Using taskName without listName may match multiple tasks`,
     inputSchema: {
         type: "object",
         properties: {
@@ -236,16 +227,15 @@ export const moveTaskTool = {
     description: `Purpose: Move a task to a different list.
 
 Valid Usage:
-1. Use taskId + (listId OR listName) - preferred
-2. Use taskName + sourceListName + (listId OR listName)
+1. Use taskId + destination list (preferred)
+2. Use taskName + sourceListName + destination list
 
 Requirements:
-- Destination list: EITHER listId OR listName REQUIRED
-- When using taskName, sourceListName is REQUIRED
+- Task identification: EITHER taskId OR (taskName + sourceListName) REQUIRED
+- Destination: EITHER listId OR listName REQUIRED
 
 Warning:
-- Task statuses may reset if destination list has different status options
-- System cannot find a task by name without knowing which list to search in`,
+- Task statuses may reset if destination list has different status options`,
     inputSchema: {
         type: "object",
         properties: {
@@ -281,18 +271,15 @@ export const duplicateTaskTool = {
     description: `Purpose: Create a copy of a task in the same or different list.
 
 Valid Usage:
-1. Use taskId + optional (listId OR listName) - preferred
-2. Use taskName + sourceListName + optional (listId OR listName)
+1. Use taskId (preferred)
+2. Use taskName + sourceListName
 
 Requirements:
-- When using taskName, sourceListName is REQUIRED
+- Task identification: EITHER taskId OR (taskName + sourceListName) REQUIRED
+- Destination: OPTIONAL - defaults to original list
 
 Notes:
-- The duplicate preserves the original task's properties
-- If no destination list specified, uses same list as original task
-
-Warning:
-- System cannot find a task by name without knowing which list to search in`,
+- The duplicate preserves the original task's properties`,
     inputSchema: {
         type: "object",
         properties: {
@@ -328,18 +315,14 @@ export const getTaskTool = {
     description: `Purpose: Retrieve detailed information about a specific task.
 
 Valid Usage:
-1. Use taskId alone (preferred) - works with both regular and custom IDs (like "DEV-1234")
-2. Use taskName + listName
-3. Use customTaskId for explicit custom ID lookup
+1. Use taskId (preferred) - works with both regular and custom IDs
+2. Use taskName + listName for targeted search 
 
 Requirements:
-- When using taskName, listName is REQUIRED
-- When using customTaskId, listName is recommended for faster lookup
+- Task identification: EITHER taskId OR (taskName + listName) REQUIRED
 
-Note:
-- Task names are only unique within a list, so the system needs to know which list to search in
-- Regular task IDs are always 9 characters long (e.g., "86b394eqa")
-- Custom IDs have an uppercase prefix followed by a hyphen and number (e.g., "DEV-1234")
+Notes:
+- Task names are only unique within a list
 - Set subtasks=true to include all subtasks in the response`,
     inputSchema: {
         type: "object",
@@ -379,12 +362,11 @@ Valid Usage:
 2. Use listName
 
 Requirements:
-- EITHER listId OR listName is REQUIRED
+- List identification: EITHER listId OR listName REQUIRED
 
 Notes:
-- Use filters (archived, statuses, etc.) to narrow down results
-- Pagination available through page parameter
-- Sorting available through order_by and reverse parameters`,
+- Use filters (archived, statuses) to narrow down results
+- Pagination and sorting available`,
     inputSchema: {
         type: "object",
         properties: {
@@ -434,12 +416,14 @@ export const getTaskCommentsTool = {
 
 Valid Usage:
 1. Use taskId (preferred)
-2. Use taskName + optional listName
+2. Use taskName + listName for targeted search
+
+Requirements:
+- Task identification: EITHER taskId OR taskName REQUIRED
 
 Notes:
-- If using taskName, providing listName helps locate the correct task
 - Task names may not be unique across different lists
-- Use start and startId parameters for pagination through comments`,
+- Use start/startId parameters for pagination`,
     inputSchema: {
         type: "object",
         properties: {
@@ -478,13 +462,11 @@ Valid Usage:
 2. Use taskName + listName
 
 Requirements:
-- EITHER taskId OR (taskName + listName) is REQUIRED
-- commentText is REQUIRED
+- Task identification: EITHER taskId OR (taskName + listName) REQUIRED
+- commentText: REQUIRED
 
 Notes:
-- When using taskName, providing listName helps locate the correct task
-- Set notifyAll to true to send notifications to all task assignees
-- Use assignee to assign the comment to a specific user (optional)`,
+- Set notifyAll=true to notify all task assignees`,
     inputSchema: {
         type: "object",
         properties: {
@@ -524,24 +506,15 @@ export const deleteTaskTool = {
     description: `Purpose: PERMANENTLY DELETE a task.
 
 Valid Usage:
-1. Use taskId alone (preferred and safest)
-2. Use taskName alone (will search across all lists)
-3. Use taskName + listName (for faster, targeted search)
+1. Use taskId (preferred and safest)
+2. Use taskName + listName for targeted search
 
 Requirements:
-- EITHER taskId OR taskName: REQUIRED
-- listName: Optional, but recommended when using taskName
-
-Notes:
-- The tool automatically searches for tasks using smart name matching
-- When only taskName is provided, it searches across all lists
-- Adding listName narrows the search to a specific list for better performance
-- Supports both regular task IDs and custom IDs (like 'DEV-1234')
+- Task identification: EITHER taskId OR taskName REQUIRED
 
 Warning:
 - This action CANNOT be undone
-- Using taskName without listName may match multiple tasks
-- If multiple matches are found, the operation will fail with a disambiguation error`,
+- Using taskName without listName may match multiple tasks`,
     inputSchema: {
         type: "object",
         properties: {

package/build/tools/task/workspace-operations.js

@@ -12,27 +12,20 @@
  */
 export const getWorkspaceTasksTool = {
     name: "get_workspace_tasks",
-    description: `Purpose: Retrieve tasks from across the entire workspace with powerful filtering options, including tag-based filtering.
+    description: `Purpose: Retrieve tasks from across the entire workspace with filtering.
 
 Valid Usage:
-1. Apply any combination of filters (tags, lists, folders, spaces, statuses, etc.)
-2. Use pagination to manage large result sets
+1. Apply any combination of filters (tags, lists, statuses, etc.)
+2. Use pagination for large result sets
 
 Requirements:
-- At least one filter parameter is REQUIRED (tags, list_ids, folder_ids, space_ids, statuses, assignees, or date filters)
-- Pagination parameters (page, order_by, reverse) alone are not considered filters
+- At least one filter parameter REQUIRED (tags, list_ids, statuses, etc.)
 
 Notes:
-- Provides workspace-wide task access (unlike get_tasks which only searches in one list)
-- Returns complete task details including descriptions, assignees, custom fields, and all metadata
-- Tag filtering is especially useful for cross-list organization (e.g., "project-x", "blocker", "needs-review")
-- Combine multiple filters to narrow down your search scope
-- Use pagination for large result sets
-- Use the detail_level parameter to control the amount of data returned:
-  - "summary": Returns lightweight task data (name, status, list, tags)
-  - "detailed": Returns complete task data with all fields (DEFAULT if not specified)
-- Responses exceeding 50,000 tokens automatically switch to summary format to avoid hitting LLM token limits
-`,
+- Searches across all lists in the workspace
+- Tag filtering allows cross-list organization
+- Set detail_level=summary for lightweight responses
+- detail_level=detailed (default) returns complete data`,
     parameters: {
         type: 'object',
         properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taazkareem/clickup-mcp-server",
-  "version": "0.6.4",
+  "version": "0.6.5",
   "description": "ClickUp MCP Server - Integrate ClickUp tasks with AI through Model Context Protocol",
   "type": "module",
   "main": "build/index.js",