Skip to main content
Glama
edrich13

MCP Jira Server

by edrich13

jira_delete_issue

Delete a Jira issue permanently by providing its issue key. Removes the issue and its data from the system.

Instructions

Delete a Jira issue permanently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe Jira issue key to delete

Implementation Reference

  • src/index.ts:275-288 (registration)
    Tool registration for 'jira_delete_issue' with input schema requiring issueKey string
    {
      name: 'jira_delete_issue',
      description: 'Delete a Jira issue permanently',
      inputSchema: {
        type: 'object',
        properties: {
          issueKey: {
            type: 'string',
            description: 'The Jira issue key to delete',
          },
        },
        required: ['issueKey'],
      },
    },
  • Handler case for 'jira_delete_issue' that calls getJiraClient().deleteIssue() and returns a success message
    case 'jira_delete_issue': {
      await getJiraClient().deleteIssue(args.issueKey as string);
      return {
        content: [
          {
            type: 'text',
            text: `Successfully deleted issue ${args.issueKey}`,
          },
        ],
      };
    }
  • JiraClient.deleteIssue() method that sends DELETE request to /issue/{issueKey} using axios
    async deleteIssue(issueKey: string): Promise<void> {
      await this.client.delete(`/issue/${issueKey}`);
    }
Behavior4/5

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

With no annotations, the description bears full burden. It discloses 'permanently' indicating irreversibility. However, it doesn't mention side effects (e.g., removal of comments, attachments) or permission requirements.

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?

A single sentence of 5 words efficiently conveys the tool's purpose. No wasted words.

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 simple one-parameter tool with no output schema, the description covers the core action. However, it could be more complete by noting the irreversible nature or typical prerequisites.

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% and the parameter 'issueKey' is well-defined. The description adds no extra meaning beyond the parameter name and schema's description; baseline 3 is appropriate.

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 a Jira issue permanently' clearly states the action (delete) and resource (Jira issue), and the word 'permanently' adds important scope. It distinguishes from sibling tools like create, update, or reading tools.

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?

No explicit guidance on when to use (e.g., only when issue is no longer needed) or when not to use (e.g., irreversible). No alternatives mentioned. Implied context from purpose but lacking.

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/edrich13/mcp-jira-server'

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