Skip to main content
Glama
Sign In
jira-mcp

jira-mcp

by nikitatsym
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

jira_delete

Permanently delete Jira resources like issues or comments by specifying an operation and parameters. Use operation 'help' to see available delete options.

Instructions

Delete Jira resources (destructive, irreversible).

Call with operation="help" to list all available delete operations. Otherwise pass the operation name and a JSON object with parameters.

Example: jira_delete(operation="DeleteIssue", params={"issue_key": "PROJ-123"})

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": {
      "operation": "<operation>"
    },
    "name": "jira_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Despite no annotations, the description discloses the key behavioral traits: destructive and irreversible. This is critical for a deletion tool, though it lacks mention of authentication or error handling.

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 sentences with clear front-loading: 'Delete Jira resources (destructive, irreversible).' Every sentence serves a purpose—identifying action, usage hint, and example.

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

Completeness3/5

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

Missing output schema and no description of return values or error handling. The help mechanism partially compensates, but for a destructive tool, more context on success/failure would improve completeness.

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?

With 0% schema coverage, the description adds an example (DeleteIssue with issue_key) but does not explain the structure of params or list all operations. It provides a help mechanism but no detailed parameter descriptions.

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 clearly states the tool deletes Jira resources and emphasizes it is destructive and irreversible. It distinguishes from siblings like jira_read, jira_write, and jira_execute by focusing solely on deletion.

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

Usage Guidelines4/5

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

Provides explicit guidance to call with operation='help' to list available delete operations, and includes a concrete example. However, it does not specify when not to use this tool or alternatives for non-destructive actions.

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

Deploy Server

Other Tools