Plane MCP Server

manage_initiative_projects

Link or unlink projects to an initiative by specifying the initiative ID, action (add/remove), and project IDs. Use list_initiative_projects to verify changes.

Instructions

Link or unlink projects of an initiative. Use list_initiative_projects to read.

Args: initiative_id: UUID of the initiative action: "add" to link the projects, "remove" to unlink them project_ids: Project UUIDs to link/unlink

Returns: The initiative's linked projects after the operation

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": {
      "initiative_id": "<initiative_id>",
      "action": "<action>",
      "project_ids": "<project_ids>"
    },
    "name": "manage_initiative_projects"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`project_ids`	Yes
`initiative_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A4.1/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the operation (link/unlink) and returns the resulting linked projects, but it does not mention error handling, idempotency, what happens if some project_ids are invalid, or whether the operation is atomic. The reversible nature is implied via 'remove' but not fully explained.

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 brief, front-loaded with the core purpose, and structured into Args and Returns. Every sentence adds value without redundancy, making it easy to parse.

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 the tool's simplicity and the presence of an output schema, the description covers the essential information: purpose, parameters, and return value. It could include edge-case behavior, but for a link/unlink operation, it is largely sufficient. The one clear alternative is mentioned, providing good contextual guidance.

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?

The input schema has 0% description coverage, but the description compensates fully by explaining each parameter: initiative_id as UUID, action with 'add' and 'remove' semantics, and project_ids as project UUIDs. It also clarifies the return value, which adds meaning beyond the schema.

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 starts with 'Link or unlink projects of an initiative' which is a specific verb+resource statement. It clearly differentiates from sibling tools like 'list_initiative_projects' by noting that the latter is for reading, making the purpose unambiguous.

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?

The description explicitly directs users to 'Use list_initiative_projects to read' when they need read access, providing a clear alternative. It does not cover broader when-not scenarios, but for the primary distinction between reading and modifying, it is sufficient.

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

Deploy Server