Skip to main content
Glama

Coline

Unlink two tasks

remove_task_relation
DestructiveIdempotent

Removes a link between tasks (a blocker, related task or duplicate). Use list_task_relations for the relationId.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "relationId": "<relationId>"
    },
    "name": "remove_task_relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
relationIdYes
taskboardIdYesBoard that has the link's source task.

Output Schema

NameRequiredDescriptionDefault
undoYes
deletedYes
removedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so safety and repeat-call behavior are covered structurally. The description adds that three distinct link types can be severed, but says nothing about reversibility, permission requirements, or what happens when the link is already absent.

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?

Two sentences, zero filler, and the link-type parenthetical is front-loaded where it matters. Nothing would be gained by trimming.

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?

Output schema exists, so return values need no explanation, and for a simple three-parameter unlink the description covers purpose, the ambiguous parameter, and the types affected. Only edge-case behavior (missing relation, permission failures) is left unstated, which is minor at this complexity.

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 schema documents workspace and taskboardId (67% coverage) but leaves relationId bare; the description compensates by naming list_task_relations as the way to obtain it, which is the one non-obvious parameter. It does not clarify the 'source task' nuance of taskboardId that the schema mentions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (removes) and resource (a link between tasks) and enumerates the link kinds — blocker, related task, duplicate — which sharpens what 'relation' means. It is clearly distinguishable from creation siblings like add_task_blocker, though it does not name that counterpart explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives actionable context by pointing to list_task_relations as the source of the required relationId, which is exactly the precondition an agent needs. It stops short of stating when an unlink should be preferred over alternatives (e.g., deleting the task) or any preconditions such as permissions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources