Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Get issue

jira_get_issue
Read-only

Read a Jira issue to retrieve its summary, status, people, description, subtasks, links, and latest comments; request raw JSON for the complete field set.

Instructions

Read an issue: summary, status, people, description as text, subtasks, links and latest comments. Set raw=true for the full Jira JSON.

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>"
    },
    "name": "jira_get_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the unprocessed Jira JSON (large).
issueYesIssue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123').
fieldsNoWith raw=true, limit to these fields.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description still adds real value by disclosing the shape of the default response (a curated text view) versus the unfiltered payload, and it warns that raw output is large. The word 'latest' hints at truncation of comments but never states the limit explicitly.

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?

Two sentences, zero filler, with the default read contract stated first and the raw-mode escape hatch second. Every clause carries information an agent needs.

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?

With no output schema, the description's field enumeration carries the burden of describing return values and does so adequately, and it points to jira_list_instances for instance naming. Gaps remain around comment truncation limits and error behavior for unknown keys, which matter for a tool that accepts keys, prefixed keys and URLs.

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 all four parameters including the prefix/URL routing rules are already documented. The description only reinforces the raw=true meaning, which the schema also states as 'unprocessed Jira JSON (large)' – marginal added meaning, so baseline 3 applies.

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 opens with a specific verb+resource ('Read an issue') and enumerates exactly what is returned: summary, status, people, text description, subtasks, links and latest comments. It does not distinguish itself from near-siblings such as jira_get_comments or jira_search, and the 'latest comments' overlap with the comments tool is left unresolved.

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

Usage Guidelines3/5

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

It gives one useful decision rule – set raw=true for the full Jira JSON – but no when-to-use versus alternatives, no statement about when a dedicated comments or search tool is preferable, and no prerequisites. Usage is implied rather than directed.

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