Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

delete_comment

Remove a specific comment from a Jira issue by providing the issue key and comment ID.

Instructions

Delete a comment from a Jira issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe issue key containing the comment
commentIdYesThe ID of the comment to delete

Implementation Reference

  • The handler case in handleCommentTool that validates args with deleteCommentSchema, calls jiraClient.deleteComment(), and returns a success message with the comment ID.
    case 'delete_comment': {
      const validatedArgs = await deleteCommentSchema.validate(args);
      const _result = await jiraClient.deleteComment(validatedArgs);
      return {
        content: [
          {
            type: 'text',
            text: `Comment ${validatedArgs.commentId} deleted successfully`,
          },
        ],
      };
    }
  • Registration of the 'delete_comment' tool in createCommentTools, with its name, description, and inputSchema (requires issueKey and commentId).
      {
        name: 'delete_comment',
        description: 'Delete a comment from a Jira issue',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The issue key containing the comment',
            },
            commentId: {
              type: 'string',
              description: 'The ID of the comment to delete',
            },
          },
          required: ['issueKey', 'commentId'],
        },
      },
    ];
  • Yup validation schema for delete_comment: requires 'issueKey' and 'commentId' as strings.
    // Schema for deleting comment
    export const deleteCommentSchema = yup.object({
      issueKey: yup.string().required('Issue key is required'),
      commentId: yup.string().required('Comment ID is required'),
    });
  • The JiraClient.deleteComment method that calls the Jira API issueComments.deleteComment() with the issue key and comment ID.
    // Delete comment
    async deleteComment(input: DeleteCommentInput) {
      try {
        const response = await this.jira.issueComments.deleteComment({
          issueIdOrKey: input.issueKey,
          id: input.commentId,
        });
        return response;
      } catch (error) {
        throw new Error(`Failed to delete comment: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • src/index.ts:78-84 (registration)
    Routing in the MCP server: when the tool name starts with 'delete_comment', it dispatches to handleCommentTool.
    } else if (
      name.startsWith('create_comment') ||
      name.startsWith('get_comments') ||
      name.startsWith('update_comment') ||
      name.startsWith('delete_comment')
    ) {
      return await handleCommentTool(name, args || {}, this.jiraClient);
Behavior2/5

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

With no annotations, the description should provide more behavioral context. It only says 'delete' without indicating if the action is permanent or reversible, or any side effects.

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

Conciseness4/5

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

The description is a single, clear sentence. It could be slightly more structured, but it is appropriately concise.

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?

For a simple delete operation with two required parameters and no output schema, the description covers the basics but lacks additional helpful context like where to obtain the commentId or the irreversibility of the action.

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% with clear parameter descriptions. The description adds no additional meaning beyond what the schema provides, earning a baseline 3.

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 verb 'Delete' and the resource 'comment', and it distinguishes this tool from siblings like create_comment or get_comments.

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?

No guidance on when to use this tool versus alternatives, or any prerequisites like permissions. The description only states the action.

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

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