Skip to main content
Glama
hackdonalds

JIRA MCP Server

by hackdonalds

Add JIRA Comment

jira_add_comment

Add comments to JIRA issues to provide updates, document progress, or communicate with team members about specific tasks.

Instructions

Add a comment to a JIRA issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe JIRA issue key
commentYesComment text

Implementation Reference

  • Handler function that executes the jira_add_comment tool: adds a comment to a JIRA issue using jiraClient.addComment and returns the result.
    async ({ issueKey, comment }) => {
      logger.info('Adding comment to JIRA issue', { issueKey });
      try {
        const addedComment = await jiraClient.addComment(issueKey, comment);
        logger.info('Successfully added comment', { 
          issueKey,
          commentId: addedComment.id
        });
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(addedComment, null, 2)
          }]
        };
      } catch (error) {
        logger.error('Failed to add comment', { issueKey, error: error.message });
        throw error;
      }
    }
  • Input schema defining parameters for jira_add_comment: issueKey (string) and comment (string).
    inputSchema: {
      issueKey: z.string().describe('The JIRA issue key'),
      comment: z.string().describe('Comment text')
    }
  • server.js:373-402 (registration)
    Registration of the jira_add_comment tool with server.registerTool, including title, description, inputSchema, and inline handler.
    server.registerTool(
      'jira_add_comment',
      {
        title: 'Add JIRA Comment',
        description: 'Add a comment to a JIRA issue',
        inputSchema: {
          issueKey: z.string().describe('The JIRA issue key'),
          comment: z.string().describe('Comment text')
        }
      },
      async ({ issueKey, comment }) => {
        logger.info('Adding comment to JIRA issue', { issueKey });
        try {
          const addedComment = await jiraClient.addComment(issueKey, comment);
          logger.info('Successfully added comment', { 
            issueKey,
            commentId: addedComment.id
          });
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(addedComment, null, 2)
            }]
          };
        } catch (error) {
          logger.error('Failed to add comment', { issueKey, error: error.message });
          throw error;
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the action is 'Add' (implying a write/mutation), but doesn't disclose permission requirements, whether comments are editable/deletable, rate limits, or response format. For a mutation tool with zero annotation coverage, this leaves critical gaps.

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?

The description is a single, direct sentence with zero wasted words. It front-loads the core purpose efficiently, making it easy to parse. Every word earns its place without redundancy.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens on success/failure, return values, error conditions, or side effects. Given the complexity of adding data to JIRA, more context is needed for safe and effective use.

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%, so the schema already documents both parameters (issueKey, comment) adequately. The description adds no additional meaning about parameter usage, constraints, or examples beyond what the schema provides, meeting the baseline for high coverage.

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 ('Add') and target resource ('comment to a JIRA issue'), making the purpose immediately understandable. It distinguishes from siblings like jira_get_issue (read) and jira_update_issue (modify fields), though it doesn't explicitly differentiate from jira_create_issue which creates a different resource type.

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. It doesn't mention prerequisites (e.g., needing an existing issue), when to choose this over jira_update_issue for communication, or any constraints. The agent must infer usage from the tool name alone.

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

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