Skip to main content
Glama

jira_delete_comment

Permanently delete a comment from a Jira issue by providing the issue key and comment ID, useful for removing outdated or incorrect comments; deletion cannot be undone.

Instructions

Permanently delete a comment from a Jira issue. This cannot be undone. You need the comment ID from jira_get_comments.

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": {
      "issueKey": "<issueKey>",
      "commentId": "<commentId>"
    },
    "name": "jira_delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYesIssue key containing the comment (e.g., KP-123)
commentIdYesID of the comment to delete (get from jira_get_comments)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose the most important trait: 'This cannot be undone,' making the destructive, irreversible nature explicit. It omits permission requirements (e.g., author vs. admin rights) and any error behavior for invalid comment IDs, which would matter for a no-annotation mutation tool.

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 short sentences, front-loaded with the action and the irreversibility warning before the parameter prerequisite. Every sentence carries a distinct fact; nothing is padding.

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 two-parameter destructive tool with no output schema and no annotations, the description covers the essentials: what is deleted, that it is permanent, and where the ID comes from. Only permission/auth expectations and failure modes are absent, which keeps it at 4.

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%, including the same 'get from jira_get_comments' note on commentId, so the schema already documents both parameters. The description's 'You need the comment ID from jira_get_comments' merely repeats that, adding no format or syntax detail (e.g., numeric vs. string IDs) beyond the schema.

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?

States a specific verb and resource: 'Permanently delete a comment from a Jira issue.' The resource noun ('comment') separates it from the other delete siblings (issue, link, worklog) without ambiguity. It stops short of explicitly naming a sibling as the contrasting alternative, so it lands at 4 rather than 5.

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 a concrete precondition: 'You need the comment ID from jira_get_comments,' which routes the agent to the sibling needed to obtain input. It does not state when not to use it (e.g., use jira_update_comment to edit instead of delete), so the exclusion side of the guidance is missing.

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