jira-mcp-server

delete_sprints

Remove one or more Jira sprints by their sprint IDs. Accepts an array of sprint identifiers to delete selected sprints.

Instructions

Delete one or more sprints

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": {
      "sprintIds": "<sprintIds>"
    },
    "name": "delete_sprints"
  }
}

Input Schema

Name	Required	Description	Default
`sprintIds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action and does not warn that deletion is permanent, mention side effects on issues within sprints, or note any permission requirements. For a destructive tool, this is insufficient.

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 one concise sentence with the key verb 'Delete' and object 'sprints' front-loaded. It is free of fluff and efficiently conveys the operation, making it appropriately sized for a simple tool.

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 the absence of output schema, annotations, and parameter descriptions, the description must provide all context. It only states the action and target, omitting important details like permanence, potential cascading effects, failure conditions, and return behavior. The tool's simplicity does not excuse this gap.

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?

The schema has a single parameter sprintIds (array of integers) with no property descriptions (schema coverage 0%). The description adds 'one or more' which implies the array should contain at least one ID, but it does not explain the meaning of the IDs or any constraints like non-empty array or maximum batch size. The low schema coverage is only partially compensated.

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 'Delete one or more sprints' clearly identifies the action (delete) and the resource (sprints), and specifies batch capability. This distinguishes it from sibling tools like delete_issues or delete_versions, which target different resources.

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?

There is no guidance on when to use this tool vs. alternatives. It does not mention prerequisites, restrictions, or scenarios where this tool is preferred over update_sprint_state or delete_issues. The description is purely the action without context.

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