Skip to main content
Glama

jira_get_issue

Retrieves a Jira issue by key or ID, returning system fields and populated custom fields, with options to include comments, worklogs, attachments, or request specific custom fields.

Instructions

Get an issue: system fields plus custom fields that currently have a value, each as {id, name, value}. Comments, worklogs, and attachments are omitted unless include lists them. Null custom fields are omitted unless customFields is "all". To fetch specific custom fields (including empty ones), pass fields as customfield_ ids or unique edit-screen names (Severity). Call jira_get_edit_meta to see writable fields; do not call jira_get_fields for an update.

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

Input Schema

NameRequiredDescriptionDefault
expandNoJira expand values in addition to names (e.g., changelog, renderedFields)
fieldsNoNarrow custom-field GET. Ids (customfield_11205) or unique editmeta names (Severity). Replaces *navigable for custom fields; requested fields are returned even if null.
includeNoCollections to include. Default omits comments, worklogs, and attachments.
issueKeyYesIssue key (e.g., KP-123) or numeric issue ID
customFieldsNoset (default): only custom fields with values. all: include navigable custom fields that are null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the important default behavior (silent omission of comments, worklogs, attachments and null custom fields) and the shape of custom field values, which the schema does not describe. However, it says nothing about failure modes, permission or visibility requirements on the issue, or size limits, which matter for a tool with zero annotation coverage.

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 lead sentence states the core behavior first, then defaults, then the field-fetching nuance, then sibling routing — a sensible front-loaded order with no filler. The third sentence is dense with parentheticals, slightly hampering scanability, but nothing is redundant.

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 five parameters, no output schema and no annotations, the description does the necessary work: it defines what is returned (system fields, populated custom fields as {id, name, value}) and what defaults are silently excluded. It leaves the shape of 'system fields' implicit, which is the main remaining gap for an agent parsing the response.

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 parameter meaning is already fully documented in the structured field. The description restates the same semantics (fields replaces *navigable, include lists collections, customFields "all") rather than adding new meaning such as format examples or interactions between fields and customFields. Baseline 3 applies.

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?

Names a specific verb+resource (get an issue) and immediately scopes it to system fields plus populated custom fields, each shaped as {id, name, value}. It also distinguishes itself from siblings by stating that comments, worklogs and attachments are excluded unless requested, so an agent can tell it apart from jira_get_comments or jira_get_worklogs.

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?

Gives explicit routing advice: call jira_get_edit_meta to see writable fields and do not call jira_get_fields for an update, which directly disambiguates against two real siblings. It also explains when to switch to customFields="all" or a fields list. It stops short of stating when not to use this tool at all (e.g. bulk retrieval), but the conditional guidance present is strong.

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