Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_delete_dependency

DestructiveIdempotent

Remove a blocking dependency between two ClickUp tasks to unblock progress. Specify the dependency direction (depends_on or dependency_of) matching creation.

Instructions

Remove a blocking dependency edge between two tasks.

Identify the edge to remove with exactly one of depends_on or dependency_of (the same direction you used to create it).

When to Use:

  • To unblock a task once its dependency no longer applies.

When NOT to Use:

  • To remove a non-blocking association — use clickup_delete_task_link.

Returns: A confirmation that the dependency edge was removed.

Examples:

  • params = {"task_id": "abc", "depends_on": "xyz"}

Error Handling: A 404 means the edge (or a task ID) does not exist; the direction must match how the dependency was originally created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. The description adds value by explaining error handling (404 means edge or task ID missing) and that direction must match creation. No contradictions with annotations.

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?

Well-structured with sections for usage, returns, examples, and error handling. Every sentence adds value, no fluff. Front-loaded with purpose.

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: usage scenarios, parameter selection rules, expected return, and error handling. The tool has moderate complexity, and the description fully equips the agent to use it correctly.

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?

Schema descriptions for parameters are present. The description goes beyond by explaining the mutual exclusivity of depends_on and dependency_of in context (same direction as creation) and provides an example, adding practical meaning.

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?

Title and description clearly state the tool removes a blocking dependency edge between tasks. It is distinct from sibling tool clickup_delete_task_link which removes non-blocking associations, and from clickup_add_dependency which adds dependencies.

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?

Explicit 'When to Use' and 'When NOT to Use' sections provide clear guidance: use to unblock a task, do not use for non-blocking associations (directs to clickup_delete_task_link). This helps the agent choose correctly.

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