Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_delete_folder

DestructiveIdempotent

Permanently delete a ClickUp folder and all its lists and tasks. This action cannot be undone.

Instructions

Permanently delete a Folder and every List/Task inside it.

Calls DELETE /folder/{folder_id}. This cannot be undone via the API.

When to Use:

  • To remove a Folder (and everything inside it) that is no longer needed.

When NOT to Use:

  • To archive instead of destroy — use clickup_update_folder semantics via the Space's archive controls, not this tool, if you may need the data again.

Returns: A confirmation string, or an Error ... string.

Examples: params = {"folder_id": "456"}

Error Handling: 404 means folder_id doesn't exist or was already deleted.

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 and cannot be undone, and includes error handling (404). Annotations already mark destructiveHint=true, but the description adds cascading deletion context 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, front-loaded key action, and no wasted words. Every sentence provides value.

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 return type (confirmation or error), error handling, and irreversibility. With an output schema present, this is fully complete for a destructive 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?

The description includes an example usage for folder_id, but the schema itself already provides a clear description. The example and additional context slightly enhance understanding.

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 the specific action 'Permanently delete a Folder and every List/Task inside it.' It uses strong verbs and resource, distinguishing it from siblings like delete_list or update_folder.

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?

Explicitly provides 'When to Use' and 'When NOT to Use' sections, with an alternative (archive via clickup_update_folder). This leaves no ambiguity for the agent.

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