Skip to main content
Glama
Sign In
Plane MCP Server

Plane MCP Server

by leigangzhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_milestone

Delete a milestone from a Plane project by supplying the project ID and milestone ID.

Instructions

Delete a milestone by ID.

Args: project_id: UUID of the project milestone_id: UUID of 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": "delete_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
milestone_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the burden of behavioral disclosure. While 'delete' implies destructive action, it does not mention irreversibility, side effects, permissions, or error behavior. This is a significant gap for a mutation tool.

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, front-loaded with the primary action, and uses a clear structured Args block. No unnecessary words.

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 delete with two parameters, the description covers the action and inputs adequately. However, it omits behavioral details like permanence, dependent data handling, or response behavior, and lacks usage context. It is a minimum viable description but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description provides the only parameter meaning. It clarifies that project_id is the UUID of the project and milestone_id is the UUID of the milestone, but does not explain the relationship between them or why both are needed.

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 'Delete a milestone by ID', which is a specific verb+resource. It distinguishes itself from sibling tools like create_milestone, update_milestone, retrieve_milestone, and list_milestones.

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?

The description gives no guidance on when to use this tool vs alternatives, no prerequisites, and no exclusions or warnings. It simply states the action and arguments.

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