Skip to main content
Glama
Sign In
Plane MCP Server

Plane MCP Server

by leigangzhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

manage_milestone_work_items

Add or remove work items from a milestone in a single request. Pass add_ids and remove_ids to batch update milestone assignments.

Instructions

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

At least one of add_ids or remove_ids must be provided.

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

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>",
      "milestone_id": "<milestone_id>"
    },
    "name": "manage_milestone_work_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
add_idsNo
project_idYes
remove_idsNo
milestone_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

A4/5.0
Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It only states the basic add/remove action and the parameter constraint. It omits important behavioral details such as error handling, idempotency, behavior when overlapping add/remove IDs are supplied, permissions, or whether the operation is atomic beyond 'in a single call.'

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 short and front-loaded with the primary action. The Args list is cleanly structured, and every sentence earns its place with no redundancy.

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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers the operation, the prerequisite constraint, and all parameter meanings. It lacks return value details and error scenarios, but is otherwise sufficient for an agent to invoke the tool correctly.

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 has no parameter descriptions, but the Args section explains each parameter with UUID semantics and clarifies the relationship between add_ids and remove_ids via the 'at least one' constraint. This adds meaningful value, though it doesn't address edge cases like empty arrays.

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 states 'Add or remove work items on a milestone in a single call.' This uses a specific verb+resource combination and uniquely identifies the tool's function, distinguishing it from siblings like list_milestone_work_items and manage_cycle_work_items.

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?

Clear context is given: the tool is for adding/removing work items on a milestone, and the 'At least one of add_ids or remove_ids must be provided' rule guides usage. However, it does not explicitly mention alternatives or exclusions (e.g., when to use list_milestone_work_items).

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

Deploy Server

Other Tools