Skip to main content
Glama
rafadepaula

@rafadepaula/clickup-mcp

by rafadepaula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

clickup_add_task_dependency

Set a directional ClickUp dependency so one task blocks another or waits on it; use waiting_on or blocking to define whether task_id cannot start or is blocking depends_on.

Instructions

Set a directional dependency where one task blocks the other. Use 'waiting_on' when task_id cannot start until depends_on is done, or 'blocking' when task_id is blocking depends_on. For non-blocking associations, use add_task_link instead.

Input Schema

NameRequiredDescriptionDefault
typeYesType of dependency to add: 'waiting_on' or 'blocking'.
task_idYesID of the task to set the dependency on. Works with regular and custom IDs (like 'DEV-1234'). Use clickup_search to find task ID by name if needed.
depends_onYesID of the task that task_id depends on or is blocking. Works with regular and custom IDs.
workspace_idNoWorkspace ID (digits only). Only needed when you have multiple workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the directional semantics of the dependency, which is important, but does not mention permissions, idempotency, side effects on existing dependencies, or likely error conditions.

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?

Three concise sentences with the core behavior front-loaded, followed by enum semantics and an alternative-tool redirect. No unnecessary repetition or filler.

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

Completeness4/5

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

For a simple mutation tool with fully documented parameters and no output schema, the description gives enough information to call it correctly and choose the right dependency type. It could be stronger by noting permission requirements or what happens if the dependency already exists, but the core operational semantics are complete.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining exactly what 'waiting_on' and 'blocking' mean in terms of task ordering, and it clarifies the directional roles of task_id and depends_on.

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?

States a specific verb and resource ('Set a directional dependency') and immediately clarifies the two directional modes. It also explicitly distinguishes the tool from the sibling 'add_task_link' for non-blocking associations.

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 says when to use 'waiting_on' versus 'blocking' and names the alternative tool for non-blocking associations. This gives an agent clear routing guidance without needing to infer from schemas.

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

Deploy Server

Other Tools