Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Add comment

jira_add_comment

Add a comment to a Jira issue with light Markdown support. Target issues by key, instance-prefixed key, or browse URL, with automatic routing to the correct Jira instance.

Instructions

Add a comment to an issue (light Markdown supported).

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": {
      "issue": "<issue>",
      "body": "<body>"
    },
    "name": "jira_add_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
issueYesIssue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123').
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful behavioral detail (light Markdown rendering in the body), but says nothing about what is returned, whether notifications fire, or what happens with an invalid issue key.

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?

One short sentence with the verb and resource front-loaded and zero redundant wording. The parenthetical Markdown note earns its place by conveying real formatting behavior.

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 mutation with annotations and no output schema, the definition covers the core action but leaves the agent guessing about the response (e.g., whether a comment ID is returned) and failure modes such as unknown issue keys or missing permissions. Adequate but with clear gaps.

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 67%: the 'issue' parameter is richly documented with key, instance-prefixed key, and URL forms, and 'instance' explains routing. The 'body' parameter has only minLength in the schema, and the description compensates partially by noting Markdown support, which is the main added semantic value.

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 ('Add a comment to an issue') plus a formatting capability ('light Markdown supported'), so the operation is unambiguous. It does not distinguish itself from siblings like jira_get_comments, but the verb makes the distinction self-evident.

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?

There is no guidance on when to use this tool, prerequisites (issue must exist, permissions needed), or any alternative such as updating the issue description instead. Usage is only implied by the verb.

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