Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_add_task_link

Link two tasks with a non-blocking 'related to' association to cross-reference them without enforcing execution order.

Instructions

Link two tasks with a non-blocking "related to" association.

Unlike dependencies, a link implies no execution order — it just cross- references two tasks. Only task-to-task links are supported (not links to other object types or arbitrary URLs).

When to Use:

  • To relate tasks that reference each other without blocking either one.

When NOT to Use:

  • To enforce completion order — use clickup_add_dependency.

Returns: A confirmation naming both linked tasks.

Examples:

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

Error Handling: A 404 means one of the task IDs is wrong; set custom_task_ids + team_id to reference tasks by custom ID.

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 indicate it's a write operation (readOnlyHint=false) and non-idempotent, but the description adds valuable behavioral context: only task-to-task links are supported, returns a confirmation naming both tasks, and explains 404 error handling. This goes beyond what annotations alone provide.

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 (purpose, when to use/not, returns, examples, error handling). Every sentence is informative and no word is wasted, making it highly efficient.

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?

Given an output schema exists, the description wisely summarizes the return type without over-explaining. It covers error handling and constraints (task-to-task only). However, it omits details like idempotency or rate limits, but these are partially covered by annotations.

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

Parameters3/5

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

The input schema already provides descriptions for all parameters (100% coverage despite context signal), so the description adds limited extra semantic value. It covers the non-blocking nature and error conditions but does not significantly enhance parameter 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 'Link two tasks with a non-blocking "related to" association', specifying the action, resource, and linkage type. It distinguishes itself from siblings like clickup_add_dependency by emphasizing the non-blocking nature.

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?

The description includes explicit 'When to Use' and 'When NOT to Use' sections, providing clear context for when this tool is appropriate and directing the user to clickup_add_dependency for completion order enforcement.

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