Skip to main content
Glama
KS-GEN-AI

Jira MCP Server

by KS-GEN-AI

delete_ticket

Remove a Jira issue permanently by specifying its ID or key to clean up resolved or obsolete tickets.

Instructions

Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in your query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdOrKeyYesThe issue id or key

Implementation Reference

  • Core handler function that executes the DELETE request to the Jira API to delete the ticket specified by issueIdOrKey.
    async function deleteTicket(issueIdOrKey: string): Promise<any> {
      try {
        const response = await axios.delete(
          `${JIRA_URL}/rest/api/3/issue/${issueIdOrKey}`,
          {
            headers: getAuthHeaders().headers,
          },
        );
        return response.data;
      } catch (error: any) {
        return {
          error: error.response.data,
        };
      }
    }
  • src/index.ts:142-155 (registration)
    Registers the 'delete_ticket' tool in the list of available tools, including its description and input schema.
      name: 'delete_ticket',
      description:
        'Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in your query.',
      inputSchema: {
        type: 'object',
        properties: {
          issueIdOrKey: {
            type: 'string',
            description: 'The issue id or key',
          },
        },
        required: ['issueIdOrKey'],
      },
    },
  • Dispatch handler in the CallToolRequestHandler that handles calls to 'delete_ticket', validates input, invokes deleteTicket, and formats the response.
    case 'delete_ticket': {
      const issueIdOrKey: any = request.params.arguments?.issueIdOrKey;
    
      if (!issueIdOrKey) {
        throw new Error('Issue id or key is required');
      }
    
      const response = await deleteTicket(issueIdOrKey);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the delete_ticket tool, specifying the required 'issueIdOrKey' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        issueIdOrKey: {
          type: 'string',
          description: 'The issue id or key',
        },
      },
      required: ['issueIdOrKey'],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool deletes a ticket but fails to disclose critical behavioral traits such as whether deletion is permanent, requires specific permissions, has side effects (e.g., cascading deletions), or involves rate limits. The mention of 'Do not use markdown in your query' is irrelevant to behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but includes an irrelevant sentence about markdown that does not contribute to understanding the tool. It is front-loaded with the core purpose, but the second sentence wastes space. Overall, it could be more concise by removing the extraneous instruction.

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 complexity of a deletion operation, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permanence, permissions), error handling, or what happens post-deletion. For a destructive tool, this leaves significant gaps for an AI agent to use it correctly.

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, clearly documenting the 'issueIdOrKey' parameter. The description does not add any meaning beyond the schema, such as examples or format details (e.g., key format like 'PROJ-123'). Baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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 action ('Delete') and resource ('a ticket on Jira'), specifying the API endpoint. However, it does not distinguish this tool from sibling tools like 'edit_ticket' or 'create_ticket' beyond the verb, nor does it clarify if deletion is permanent or reversible.

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 (e.g., 'edit_ticket' for modifications or 'execute_jql' for querying). It includes an unrelated instruction about markdown, which does not aid in tool selection. No explicit when/when-not scenarios or prerequisites are mentioned.

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/KS-GEN-AI/jira-mcp-server'

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