Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

atlassian-mcp__jira_delete_issue

Destructive

Permanently delete a Jira issue. THIS CANNOT BE UNDONE through the API — deleted issues do not go to a trash or archive, and the issue key is not reused, so every link to it breaks. Prefer transitioning the issue to Done or Won't Do, which keeps the history. Deleting an issue that has subtasks fails unless delete_subtasks is true, in which case the subtasks are destroyed with it. Deleting a parent does not delete linked issues, only subtasks.

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": "atlassian-mcp__jira_delete_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
issue_keyYesThe issue key to delete (e.g. PROJ-123)
delete_subtasksNoAlso delete the issue's subtasks. Required to be true when the issue has any — without it Jira rejects the whole call rather than deleting partially. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnly=false, but the description adds substantive consequences beyond that: no trash/archive, issue key not reused, inbound links break, subtasks destroyed when delete_subtasks is true, and linked issues surviving a parent delete. It stops short of noting permission or rate-limit requirements, which keeps it from a 5.

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 permanence warning is front-loaded in all caps, followed by the safer alternative and then the subtask edge case. Every sentence conveys an operational fact an agent needs, with no filler.

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 destructive, three-parameter tool with no output schema, the description covers irreversibility, the recommended alternative, the subtask precondition, and link/subtask side effects. Nothing needed to call it correctly or decide against calling it is missing.

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%, so issue_key, account, and delete_subtasks are already documented, and the description largely restates the delete_subtasks semantics rather than adding new meaning. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence states a specific verb and resource ('Permanently delete a Jira issue'), and the second and third sentences scope it further by contrasting it with the safe alternative of transitioning to Done/Won't Do. An agent can distinguish this from jira_transition_issue and jira_update_issue without opening any schema.

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

Usage Guidelines5/5

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

The description gives explicit when-not guidance ('Prefer transitioning the issue to Done or Won't Do, which keeps the history') and states a concrete precondition for the delete_subtasks path. It leaves no ambiguity about the preferred alternative or the failure mode to avoid.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources