HacknPlan MCP

delete_milestone

Delete a milestone permanently from a project, with options to also remove its boards and work items.

Instructions

Permanently delete a 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": {
      "projectId": "<projectId>",
      "milestoneId": "<milestoneId>"
    },
    "name": "delete_milestone"
  }
}

Input Schema

Name	Required	Description
`projectId`	Yes
`milestoneId`	Yes
`deleteBoards`	No	Also delete all boards in this milestone (default false)
`deleteWorkItems`	No	Also delete all work items (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description only notes permanence but does not disclose side effects of optional booleans, permission requirements, or reversibility. With no annotations, the description carries full burden and fails to provide sufficient behavioral context.

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

Conciseness3/5

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

The description is a single short sentence, front-loaded with action. However, it is under-specified for a mutation tool with 4 parameters.

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

Completeness2/5

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

Given no annotations, no output schema, and 4 parameters (some with schema descriptions), the description is insufficient. It lacks explanation of child object behavior and user impact.

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

Parameters2/5

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

Schema coverage is 50%; two parameters have descriptions in schema. The tool description adds no additional meaning beyond the title. It does not explain projectId, milestoneId, or the effects of the boolean flags.

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 verb 'delete' and resource 'milestone', and 'permanently' adds finality. It distinguishes from siblings like 'close_milestone' which is non-destructive.

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 on when to use this tool versus alternatives like 'close_milestone'. No prerequisites or context provided.

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

Deploy Server