Plane MCP Server

attach_page_to_work_item

Link a page to a work item by supplying the project ID, work item ID, and page ID, creating a direct association.

Instructions

Link a page to a work item.

Args: project_id: UUID of the project work_item_id: UUID of the work item page_id: UUID of the page to link

Returns: WorkItemPage link object

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": {
      "project_id": "<project_id>",
      "work_item_id": "<work_item_id>",
      "page_id": "<page_id>"
    },
    "name": "attach_page_to_work_item"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes
`project_id`	Yes
`work_item_id`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`page`	No
`issue`	No
`project`	No
`workspace`	No
`created_at`	No
`created_by`	No
`updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the entire burden of behavioral disclosure. It only states the action and return type, but does not mention side effects (e.g., whether an existing link is replaced, whether the operation is idempotent), potential errors, or permission requirements. This is a significant gap for a mutation-like tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and well-structured with an Args/Returns format. The main action sentence is front-loaded. However, it is slightly redundant with the schema (repeating parameter names), but it remains efficient and scannable.

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

Completeness3/5

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

For a simple link operation with three parameters and an output schema, the description covers the core information. However, it lacks important context such as idempotency, duplicate-link behavior, or required preconditions. Given the lack of annotations and the presence of sibling tools that manage links, a bit more detail would make it fully 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?

The input schema only defines parameter names and types (string), with no descriptions. The description adds meaning by explaining each parameter's role and specifying they are UUIDs (e.g., 'UUID of the project', 'UUID of the work item', 'UUID of the page to link'). This directly compensates for the 0% schema description coverage.

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: 'Link a page to a work item.' It names the specific verb (link/attach) and the resources involved (page, work item), and the distinction from sibling tools like 'detach_page_from_work_item' is evident. The mention of return object ('WorkItemPage link object') further clarifies its purpose.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention that this is the counterpart to 'detach_page_from_work_item', nor does it explain any prerequisites (e.g., existence of the page and work item, user permissions). The description simply states what it does without contextual usage direction.

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

Deploy Server