clickup_get_taskFetch full task details including name, description, status, priority, assignees, tags, and time tracking. Provide task ID (e.g., "9hz6c").
| Name | Required | Description | Default |
|---|---|---|---|
| _apiKey | Yes | ClickUp API token | |
| task_id | Yes | Task ID |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds value by specifying exact fields returned, confirming safe read behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with key information, no redundant text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists, parameters fully documented, description lists returned fields. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. Description only adds example for task_id, no extra semantics beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it fetches full task details and lists specific fields (name, description, status, etc.). It distinguishes from sibling tools like clickup_list_tasks, and includes resource identifier format.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides basic guidance to provide task ID, but no explicit when-to-use vs alternatives. Acceptable given clear name and context from siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have distinct purposes, but there is overlap among query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) and among prediction market tools. Detailed descriptions help differentiate, but the large number of tools increases chance of misselection.
Naming is highly inconsistent, mixing snake_case and camelCase conventions. ClickUp tools use 'clickup_' prefix while Pipeworx tools have varied patterns (ask_, scan_, validate_, etc.). No unified convention across the set.
35 tools is excessive for a server named 'Clickup', with only 6 ClickUp-specific tools. The remaining 29 are from Pipeworx, which is unrelated. The count is inappropriate for the server's stated purpose.
The ClickUp integration is incomplete, missing basic CRUD operations like update and delete tasks. The Pipeworx side is comprehensive but not relevant to the server's name. For a ClickUp server, coverage is poor.