Plane MCP Server

manage_cycle_work_items

Add work items to a cycle or remove them from it in a single API call. Provide project and cycle IDs, then specify item IDs to add, remove, or both.

Instructions

Add or remove work items on a cycle in a single call.

At least one of add_ids or remove_ids must be provided.

Args: project_id: UUID of the project cycle_id: UUID of the cycle add_ids: UUIDs of work items to add to the cycle remove_ids: UUIDs of work items to remove from the cycle

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>",
      "cycle_id": "<cycle_id>"
    },
    "name": "manage_cycle_work_items"
  }
}

Input Schema

Name	Required	Description	Default
`add_ids`	No
`cycle_id`	Yes
`project_id`	Yes
`remove_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A3.7/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 full burden of behavioral disclosure. It states the mutation action and the single-call behavior, but does not disclose essential traits such as whether the operation replaces existing cycle membership, how duplicates are handled, permissions required, or reversibility. For a mutation tool, this is a significant transparency gap.

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 concise and front-loaded with the core action, followed by a key constraint and a terse parameter list. Every sentence contributes useful information without redundancy, making it appropriately sized for an AI agent.

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?

The tool has no output schema and no annotations, so the description must supply return-value and side-effect expectations. It does not mention what the response contains or whether the operation is additive/subtractive to existing membership. While the basic operation is clear, completeness is limited for an agent to predict outcomes fully.

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 description coverage is 0%, so the description must compensate. It does so with an Args section explaining each parameter by role and type, and explicitly notes the constraint that at least one of add_ids or remove_ids is required. This adds meaningful meaning beyond the bare schema, though it could be more detailed about expected item formats or validation.

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 tool's function: 'Add or remove work items on a cycle in a single call.' This specific verb+resource distinguishes it from siblings like list_cycle_work_items (read-only) and transfer_cycle_work_items (moving items between cycles).

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

Usage Guidelines3/5

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

The description implies usage through its core statement and adds a prerequisite ('At least one of add_ids or remove_ids must be provided'). However, it does not explicitly mention when to use this tool versus alternatives like transfer_cycle_work_items, nor does it offer exclusions. The usage context is clear but not fully differentiated.

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

Deploy Server