Taiga MCP Server

Delete User Story

user_story_delete

Destructive

Delete a user story by ID after confirmation. Prevents accidental deletion: clients either confirm interactively or review a preview and confirm explicitly.

Instructions

Delete a user_story by id. This cannot be undone. Requires confirmation: elicitation-capable clients are prompted interactively; others must call again with confirm: true after reviewing the preview returned by the first call.

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": {
      "id": "<id>"
    },
    "name": "user_story_delete"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Resource id
`confirm`	No	Set true to actually delete after reviewing the preview from a first call without it. Ignored by elicitation-capable clients, which are prompted interactively instead.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description goes well beyond annotations by disclosing irreversibility ('This cannot be undone') and the confirmation workflow (interactive prompt for elicitation-capable clients, confirm:true for others). This is exactly the kind of behavioral context that helps an agent handle a destructive operation safely.

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 compact and front-loaded. The first sentence states the essential action, the second emphasizes irreversibility, and the third details the confirmation flow. Every sentence contributes necessary information without redundancy or 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?

The description covers purpose, irreversibility, confirmation, and the preview from the first call. It does not specify the exact response format (no output schema exists), but for a delete tool with two-step confirmation, the key behavior and prerequisites are well covered.

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 100% for both parameters, so the schema already explains 'id' and 'confirm' thoroughly. The description mentions confirmation behavior but does not add significant new parameter-level semantics beyond what the schema already provides.

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 user_story by id', using a specific verb and resource. It distinguishes this tool from siblings like user_story_update and user_story_get, and the two-step confirmation behavior is immediately tied to the delete action.

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?

The description clearly explains when to use the tool (to delete a user_story) and provides important usage context (requires confirmation, cannot be undone). It does not explicitly compare to alternatives, but the tool's role is unambiguous given the sibling list and the single-purpose delete action.

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

Deploy Server