Skip to main content
Glama

jira_delete_issue

Permanently delete a Jira issue by key; set deleteSubtasks=true when the issue has subtasks to avoid failed deletion. This action cannot be undone.

Instructions

Permanently delete a Jira issue. WARNING: This action cannot be undone. If the issue has subtasks, you must set deleteSubtasks=true or the deletion will fail. Consider transitioning to a "Cancelled" or "Won't Do" status instead of deleting.

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": {
      "issueKey": "<issueKey>"
    },
    "name": "jira_delete_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYesIssue key to delete (e.g., KP-123)
deleteSubtasksNoSet to true to also delete all subtasks. Required if the issue has subtasks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does much of it: it declares the operation irreversible and warns that deletion will fail on an issue with subtasks unless deleteSubtasks=true. It omits whether the caller needs admin/delete-issue permission, whether deleted issues are recoverable from a trash, and what the response contains.

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?

Four short sentences, front-loaded with the action and the irreversibility warning before the operational caveat and the safer alternative. No filler or redundant restatement of the name.

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?

For a two-parameter destructive tool with no annotations and no output schema, the description covers the essential decision inputs: irreversibility, the subtask failure mode, and a safer alternative path. Permission requirements and return behavior are the only material gaps.

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 is 100%, so both parameters and their example format are already documented in the schema; the description's job is to add meaning beyond that. It reinforces the conditional failure semantics of deleteSubtasks ('or the deletion will fail'), which slightly exceeds the schema's 'Required if the issue has subtasks', but it adds nothing about issueKey's format beyond the schema example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Permanently delete a Jira issue'), and 'permanently' plus 'issue' distinguish it from the sibling delete tools for comments, links, and worklogs. It stops short of explicitly naming those siblings, but no ambiguity remains about what gets deleted.

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?

It supplies a concrete alternative ('Consider transitioning to a "Cancelled" or "Won't Do" status instead of deleting'), steering the agent toward jira_transition_issue for the non-destructive case, and it names the precondition that makes deletion fail (existing subtasks without deleteSubtasks=true). It does not state when deletion is actually the right call (e.g., duplicates, spam) or the permissions required.

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