Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_add_dependency

Create a blocking dependency to enforce task execution order. Specify if a task waits on or blocks another task.

Instructions

Create a blocking dependency between two tasks.

A dependency says one task must be completed before another. Pick the direction with exactly one of depends_on (task_id waits on that task) or dependency_of (task_id blocks that task) — the other end is task_id.

When to Use:

  • To enforce an execution order ("finish design before build").

  • To surface blockers on the ClickUp task's Relationships tab.

When NOT to Use:

  • For a loose "related to" association with no ordering — use clickup_add_task_link instead.

  • To remove an edge — use clickup_delete_dependency.

Returns: A confirmation naming both tasks and the direction of the new edge.

Examples:

  • task_id waits on another task: params = {"task_id": "abc", "depends_on": "xyz"}

  • task_id blocks another task (with custom IDs): params = {"task_id": "PROJ-1", "dependency_of": "PROJ-2", "custom_task_ids": true, "team_id": "123"}

Error Handling: A 400/403 usually means the Dependencies ClickApp is disabled for the Workspace or the plan does not include it; a 404 means a task 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?

The description explains the dependency creation behavior in detail, including direction mutual exclusivity, required parameters, and return value. It also covers error handling (400/403/404) for common issues. Annotations are non-contradictory and the description adds significant behavioral context beyond them.

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-organized with clear sections, front-loaded with the core purpose, and each sentence adds value. It is concise yet comprehensive, with no fluff.

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?

Given the presence of an output schema (confirmation), the description appropriately mentions the return value. It also covers error handling and provides examples, making it complete for an agent to use effectively.

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

Parameters5/5

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

Despite context indicating 0% schema description coverage, the description adds essential parameter semantics: explains mutual exclusivity of depends_on/dependency_of, clarifies custom_task_ids usage, and gives concrete examples. This compensates fully for any schema gaps.

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 action: 'Create a blocking dependency between two tasks.' It explains the concept of dependency direction and distinguishes from related tools like clickup_add_task_link and clickup_delete_dependency, ensuring the agent understands exactly what this tool does.

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 context: enforce execution order or surface blockers, and contrast with clickup_add_task_link for loose associations and clickup_delete_dependency for removal. Examples further guide correct usage.

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