clickup_delete_task
Permanently delete a ClickUp task by providing its unique task ID.
Instructions
Permanently delete a task
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | ClickUp task ID |
Permanently delete a ClickUp task by providing its unique task ID.
Permanently delete a task
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | ClickUp task ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The word 'Permanently' indicates irreversibility, but the description does not disclose cascading effects (e.g., deletion of subtasks or comments) or required permissions. Since no annotations are provided, more detail would be helpful.
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?
Extremely concise (three words) and front-loaded. No unnecessary information.
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?
For a simple one-parameter tool with no output schema, the description is sufficient. It clearly communicates the core functionality.
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?
The only parameter task_id is fully described in the schema. The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.
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?
The description clearly states the action (delete) and the resource (task). It is specific and distinguishes from sibling tools that delete other entities.
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?
No guidance on when to use this tool versus alternatives like clickup_delete_list or clickup_delete_checklist. The description lacks context about prerequisites or when deletion is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cvrt-jh/clickup-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server