Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_delete_task

DestructiveIdempotent

Permanently deletes a ClickUp task and its subtasks. Use when you are certain the task should be removed entirely, not just closed or archived.

Instructions

Permanently delete a task.

Calls DELETE /task/{task_id}. This removes the task (and its subtasks); it cannot be undone via the API. Set custom_task_ids=true (+ team_id) to address the task by Custom Task ID.

When to Use:

  • To remove a task you are certain should be gone.

When NOT to Use:

  • To merely close or archive a task — use clickup_update_task (status / archived).

Returns: A confirmation string.

Examples:

  • params = {"task_id": "86cxy1"}

Error Handling: 404 means the task is already gone or the id is wrong.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that deletion is permanent, removes subtasks, cannot be undone via API, and describes error handling (404). Annotations already indicate destructive and idempotent, and the description adds specific consequences without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections, each sentence adds value. It is concise yet comprehensive, with no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all necessary aspects: purpose, permanence, prerequisites, error handling, and alternatives. With annotations and output schema present, the description is fully adequate for a delete tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is reported as 0%, the description explains custom_task_ids and team_id usage with an example. Some parameter details (like task_id format) are left to the schema, but overall adds value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it permanently deletes a task, mentions the HTTP method, and distinguishes from close/archive (via sibling clickup_update_task). It is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'When to Use' and 'When NOT to Use' sections, directing users to use clickup_update_task for close/archive. Also explains custom_task_id usage and workspace id requirement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/trustxai/clickup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server