Loading ToolBench

Reading the current corpus…

clickup-mcp MCP server · D · ToolBench

clickup-mcp

Model Context Protocol server for interacting with ClickUp API, providing tools for managing teams, spaces, folders, lists, tasks, and documents

2026-07-28+STDIO29 tools

51/100

Definition Quality71

Protocol Readiness50

Supportability18

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

ClickUp MCP has 29 tools with consistent naming (verb_noun pattern) and basic schemas. However, parameter descriptions are sparse or missing entirely. Most tools lack output schema documentation. Error handling is minimal, no recovery guidance or actionable error messages. Descriptions average ~60 chars, below the 194-char baseline for A+ tools. Tool composition is sound (single responsibility), but parameter constraints (enums, ranges) are largely absent. Security: API key properly injected via environment variable. No tool annotations (readOnlyHint/destructiveHint) despite clear risk stratification in the tool list.

Tools (29)

bulk-create-taskswriteauthsource verified75/100

Creates multiple tasks in ClickUp

bulk-delete-tasksdestructiveauthsource verified70/100

Deletes multiple tasks in ClickUp by iterating through IDs

bulk-update-taskswriteauthsource verified75/100

Updates multiple tasks in ClickUp by iterating through task update objects

create-documentwriteauthsource verified75/100

Creates a new document

create-folderwriteauthsource verified73/100

Creates a new folder in a space

create-folder-from-templatewriteauthsource verified73/100

Creates a new folder from a template

create-listwriteauthsource verified75/100

Creates a new list in a folder

Issues (5)

HIGHtool ↗

Output schemas not documented. Tools return data but LLMs cannot predict field structure, forcing trial-and-error parsing. Breaks tool chaining (e.g., get-teams returns team_id but downstream tools may not know to extract it).

get-teamsget-spacesget-spaceget-foldersget-folderget-listsget-tasksget-tasksearch-documentsget-documentget-doc-pagesget-page

HIGHtool-description ↗

Parameter descriptions missing or trivial. 'Space color' does not explain format (hex, RGB, name?). 'Features object' lacks structure. LLMs cannot validate input without explicit constraints.

update-spacecreate-folder-from-templatecreate-listupdate-taskcreate-document

HIGHconstrained-input ↗

No enum constraints on categorical parameters. 'status' (update-task), 'priority' (create-task), 'archived' (create-folder-from-template) accept free-form strings. LLMs hallucinate invalid values.

Recommendations

Add output schema documentation to every tool. Example: 'Returns: {teams: [{id: string, name: string, color: string}], total: number}'. This enables LLMs to chain tools and extract the right fields.
Expand parameter descriptions to 50 - 150 chars with format/constraint hints. E.g., 'Space color (hex code: #RRGGBB or named color: red, blue, green)' instead of 'Space color'.
Replace free-form string parameters with enums where values are known. E.g., priority: enum [1, 2, 3, 4] with descriptions (1=urgent, 4=low). status: enum [open, in_progress, closed].
Add tool annotations to schema. Mark destructive tools with destructiveHint: true, read-only tools with readOnlyHint: true. This enables MCP clients to apply safety policies.
Implement error recovery guidance. Catch API errors and return structured responses: {error: 'User not found', suggestion: 'Try search_users() with a partial name', retryable: false}.

Score history

Overall score trend

First recorded score · v2 rubric

51/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	51	2026-07-28+	v2