Loading ToolBench
An intelligent Model Context Protocol server for ClickUp API integration with 157 tools, AI-powered efficiency optimization, smart tool suggestions, and context-aware workflow recommendations
ClickUp MCP server demonstrates moderate quality across 24 tools with consistent naming conventions and adequate descriptions. Most tools follow verb_noun naming (clickup_get_*, clickup_create_*, clickup_update_*, clickup_delete_*), which aligns with pattern:tool standards. Descriptions are present and mostly actionable (range: 80-280 chars), falling within acceptable bounds. However, several critical issues emerge: (1) No explicit input schema definitions visible in the provided source, tool schemas are inferred from the request data structure, not explicitly registered. (2) Parameter descriptions exist but lack detailed format specifications, ranges, and constraints that LLMs need for safe input generation. (3) Output schemas are undocumented, LLMs cannot anticipate response structure. (4) Error handling is minimal; no recovery guidance or categorization visible. (5) One tool 'clickup_create_task_comment_raw_test' appears to be a debug/test artifact, not production-grade. (6) Some parameters use generic identifiers without guidance on resolution (e.g., 'user_ids' as strings vs numbers). The monorepo structure and comprehensive tool coverage (157 tools claimed; 24 sampled) suggest ambition, but schema registration and output documentation are the weak points limiting production confidence.
Create multiple tasks in a ClickUp list in a single operation. More efficient than creating tasks individually. Supports up to 50 tasks per request.
⚠️ DESTRUCTIVE: Delete multiple tasks from ClickUp in a single operation. This action cannot be undone and will permanently remove all specified tasks.
Update multiple tasks in ClickUp in a single operation. More efficient than updating tasks individually. Supports up to 50 tasks per request.
Create a new chat channel in a workspace with specified name, description, topic, members, and visibility.
Create a chat channel on a specific space, folder, or list for contextual discussions. The channel name is derived from the location.
No explicit input/output schemas visible in source code, tool definitions are inferred from parameter lists rather than registered via SDK.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 55 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Create a new checklist in a ClickUp task. Returns the created checklist details.
Create a new item in a ClickUp checklist. Supports optional assignee and resolved status (resolved is applied via a follow-up update, since the create endpoint does not accept it). Returns the full parent checklist including all items.
Create a direct message channel with up to 15 users. Provide no user IDs to create a self-DM.
Create a new comment on a ClickUp task. Supports GitHub Flavored Markdown in comment text, or structured comment blocks for @mentions. Provide either comment_text or comment. Supports optional assignee and notification settings.
RAW API TEST: Create a comment bypassing ALL MCP processing to isolate duplication issue. Returns raw ClickUp API response.
Delete a checklist from a ClickUp task. Removes the checklist and all its items.
Delete an item from a ClickUp checklist.
⚠️ DESTRUCTIVE: Delete a subtask from ClickUp. This action cannot be undone and will permanently remove the subtask.
List attachments for a task or a File custom field using the ClickUp v3 API. Results are cursor-paginated; pass next_cursor from a previous response to fetch the next page.
Retrieve detailed information about a specific chat channel by its ID.
Retrieve followers of a chat channel who receive notifications about channel activity (cursor-paginated).
Retrieve chat channels in a workspace with cursor pagination and optional filtering by channel type, follower status, and activity.
Get comments for a ClickUp chat view. Returns comment details with pagination support.
Get comments for a ClickUp task. Returns comment details including text, author, and timestamps with enhanced markdown styling.
Merge multiple tasks into a single task using ClickUp's native merge. Content from the secondary tasks (comments, attachments, and other data) is migrated into the primary task server-side. Custom Task IDs are not supported.
Update a chat channel's name, description, topic, visibility, or location.
Update an existing ClickUp checklist's name and/or position (order of appearance on the task; 0 = top). The ClickUp API returns an empty response for this operation; use get_task to see the updated state.
Update an existing ClickUp checklist item's properties including name, assignee (null to unassign), resolved status, and parent (nest under another item, or null to un-nest). Returns the full parent checklist including all items.
Upload a file to a ClickUp task as an attachment. Provide the file as base64 data (file_data), a local file path (file_path), or a URL to fetch (file_url). Files stored in the cloud must be fetched first; ClickUp only accepts the binary upload.
No documented output schemas, LLMs cannot predict response structure, breaking downstream tool chaining and context planning.
Debug/test tool in production: 'clickup_create_task_comment_raw_test' indicates incomplete work. This tool should be removed before release.
Parameter type ambiguity, many 'user_ids' and similar parameters lack format specification (string vs integer, email vs ID, constraints).
Destructive operations lack confirmation pattern, delete_checklist, delete_checklist_item, and bulk_delete_tasks have minimal safeguards.
Missing error recovery guidance, no tool descriptions mention what to do if calls fail (retryable?, user action needed?, alternatives?).
Pagination implementation inconsistent, some tools (get_chat_channels, get_chat_channel_followers) use cursor; others (get_task_comments) use start+start_id. No unified pagination guidance.
Parameter interdependencies undocumented, custom_task_ids requires team_id; comment blocks override comment_text, but dependencies not stated clearly.