Skip to main content
Glama

Delete Jira issue

delete_issue
DestructiveIdempotent

Permanently delete a Jira issue when it is no longer needed. Use the delete_subtasks option to remove an issue that has subtasks, since deletion cannot be undone.

Instructions

Permanently delete a Jira issue. Jira cannot restore it. An issue with subtasks is only deleted when delete_subtasks is true.

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": {
      "issue_key": "<issue_key>"
    },
    "name": "delete_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
config_idNoJira instance to use, from list_configs. Omit for the default.
issue_keyYesIssue key, e.g. ONE-123.
delete_subtasksNoAlso delete the issue's subtasks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description earns credit for going beyond them: it states the deletion is permanent and unrecoverable by Jira, and it discloses a concrete failure mode — an issue with subtasks is not deleted unless delete_subtasks is true. It does not mention permission requirements or what happens to comments, attachments, or links.

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 short sentences with zero waste, and the highest-risk fact (permanent, unrestorable deletion) is front-loaded before the parameter-specific caveat.

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

Completeness5/5

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

For a three-parameter destructive tool with full schema coverage and no output schema, the description supplies exactly the missing pieces an agent needs: irreversibility and the subtask-blocking rule. Any further detail (response shape, cascade effects) is secondary to calling it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description exceeds it by explaining the conditional consequence of delete_subtasks (silent non-deletion when subtasks exist and the flag is false), which the schema's 'Also delete the issue's subtasks' does not convey. config_id and issue_key remain documented only by the schema.

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 opens with a specific verb and resource — 'Permanently delete a Jira issue' — which an agent can immediately distinguish from mutation siblings like update_issue or transition_issue, since it is the only removal operation. It stops short of naming any alternative explicitly, so it does not fully meet the top-bar sibling-differentiation criterion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is only implied: the irreversibility warning hints that this should be a last resort, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to alternatives (e.g., transition_issue to close an issue instead of deleting it). The subtask conditional is a behavioral rule rather than selection guidance.

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