Skip to main content
Glama

jira_delete_issue

Delete a Jira issue by providing its issue key to remove it from your Jira instance.

Instructions

Delete a Jira issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe Jira issue key to delete

Implementation Reference

  • Core implementation of the delete issue functionality using DELETE request to Jira REST API /issue/{issueKey}
    async deleteIssue(issueKey: string): Promise<void> {
      await this.request<void>(`/issue/${issueKey}`, {
        method: "DELETE",
      });
    }
  • MCP CallTool handler case that validates input with DeleteIssueSchema and delegates to jiraClient.deleteIssue
    case "jira_delete_issue": {
      const { issueKey } = DeleteIssueSchema.parse(args);
      await jiraClient.deleteIssue(issueKey);
      return {
        content: [
          { type: "text", text: `Issue ${issueKey} deleted successfully` },
        ],
      };
  • Zod schema used for input validation in the tool handler
    const DeleteIssueSchema = z.object({
      issueKey: z.string().describe("The Jira issue key to delete"),
    });
  • src/index.ts:296-307 (registration)
    Tool registration entry in ListTools response, defining name, description, and input schema
    name: "jira_delete_issue",
    description: "Delete a Jira issue",
    inputSchema: {
      type: "object",
      properties: {
        issueKey: {
          type: "string",
          description: "The Jira issue key to delete",
        },
      },
      required: ["issueKey"],
    },
Behavior1/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 states 'Delete a Jira issue' but fails to mention critical traits like whether deletion is permanent, requires admin rights, affects linked data, or has rate limits. This is inadequate for a destructive operation.

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 a single, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core action without unnecessary elaboration.

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 tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It should address behavioral risks, permission requirements, and potential side effects to adequately guide an AI agent in a high-stakes context.

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?

The input schema has 100% description coverage, with the single parameter 'issueKey' documented as 'The Jira issue key to delete'. The description adds no additional meaning beyond this, so it meets the baseline of 3 for high schema coverage.

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 clearly states the verb ('Delete') and resource ('a Jira issue'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'jira_update_issue' or 'jira_transition_issue' in terms of destructive action, which would require a 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'jira_update_issue' for modifying issues or 'jira_transition_issue' for changing status. It lacks any mention of prerequisites, such as needing appropriate permissions or confirming deletion intent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yogeshhrathod/JiraMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server