HacknPlan MCP Server

delete_work_items

Stage and confirm deletion of one or more work items. Items are stored in recovery cache before final deletion.

Instructions

Delete one or more work items (array-based, requires confirmation). Stages items for deletion and returns a confirmation token. Call confirm_deletion with the token to execute the deletion. Items are stored in recovery cache before deletion for potential recovery.

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": {
      "workItemIds": "<workItemIds>"
    },
    "name": "delete_work_items"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	No	The project ID (optional if HACKNPLAN_DEFAULT_PROJECT set)
`workItemIds`	Yes	Array of work item IDs to delete (1-100 items)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv7.2.0Jul 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations, but description discloses key behaviors: two-step process, recovery cache, and potential recovery. Adds significant context beyond schema.

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?

Three sentences, front-loaded with purpose and process, every sentence adds value, no fluff.

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?

Completes understanding of tool behavior and next steps, though lacks explicit mention of return value format or error handling. Adequate for a tool with 2 simple params.

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 coverage 100%, so baseline 3. Description repeats array nature but adds no new meaning to parameters.

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?

Clearly states deletion of work items with array input and required confirmation, distinguishing from similar sibling 'batch_delete_work_items' by emphasizing the confirmation step.

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?

Provides clear guidance: stage items, get token, then call confirm_deletion. Implies when to use (not for immediate deletion) but lacks explicit when-not.

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

Deploy Server