Skip to main content
Glama
Sign In
atlassian-browser-mcp

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Issue

jira_get_issue
Read-onlyIdempotent

Retrieve detailed information for a specific Jira issue, including Epic links and relationships, and inline comments, transitions, changelog, or worklogs to avoid extra tool calls.

Instructions

Get details of a specific Jira issue.

Includes Epic links and relationship information. Use the include parameter to inline enrichments (remote_links, transitions, watchers, changelog, comments, worklogs) so that separate tool calls are not needed.

Input Schema

NameRequiredDescriptionDefault
expandNo(Optional) Fields to expand. Examples: 'renderedFields' (for rendered content), 'transitions' (for available status transitions), 'changelog' (for history)
fieldsNo(Optional) Comma-separated list of fields to return (e.g., 'summary,status,customfield_10010'). You may also provide a single field as a string (e.g., 'duedate'). Use '*all' for all fields (including custom fields), or omit for essential fields only.assignee,created,description,issuetype,labels,priority,reporter,status,summary,updated,versions
includeNo(Optional) Comma-separated sections to inline in the response, avoiding extra tool calls. Supported: all, remote_links, transitions, watchers, changelog, comments, worklogs
issue_keyYesJira issue key (e.g., 'PROJ-123', 'ACV2-642')
propertiesNo(Optional) A comma-separated list of issue properties to return
comment_limitNoMaximum number of comments to include (0 or null for no comments)
update_historyNoWhether to update the issue view history for the requesting user
use_display_namesNoWhen true, custom field keys in the output use human-readable display names (e.g. 'Story Points') instead of opaque IDs (e.g. 'customfield_10243'). The 'names' expansion is added automatically. Standard fields are unaffected.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / fields / default
      Previous value: -"labels,versions,priority,description,reporter,status,summary,created,issuetype,updated,assignee"New value: +"assignee,created,description,issuetype,labels,priority,reporter,status,summary,updated,versions"
    • changedInput schema / properties / issue_key / pattern
      Previous value: -"^[A-Z][A-Z0-9_]+-\\d+$"New value: +"^[A-Z][A-Z0-9_]+-\\d+(?:-\\d+)*$"
    • addedInput schema / properties / use_display_names
      Added value: +{
+  "default": false,
+  "description": "When true, custom field keys in the output use human-readable display names (e.g. 'Story Points') instead of opaque IDs (e.g. 'customfield_10243'). The 'names' expansion is added automatically. Standard fields are unaffected.",
+  "type": "boolean"
+}
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Changed2 schema fields changedv1.2.1
    • changedInput schema / properties / fields / default
      Previous value: -"reporter,status,priority,created,issuetype,summary,updated,labels,description,assignee"New value: +"labels,versions,priority,description,reporter,status,summary,created,issuetype,updated,assignee"
    • addedInput schema / properties / include
      Added value: +{
+  "default": null,
+  "description": "(Optional) Comma-separated sections to inline in the response, avoiding extra tool calls. Supported: all, remote_links, transitions, watchers, changelog, comments, worklogs",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / fields / default
      Previous value: -"summary,issuetype,description,status,updated,created,reporter,labels,assignee,priority"New value: +"reporter,status,priority,created,issuetype,summary,updated,labels,description,assignee"
  4. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses that Epic links and relationships are included by default and that 'include' inlines extra sections to avoid extra round-trips. It says nothing about pagination limits or response size, so it stops short of a 5.

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?

Three short sentences, front-loaded with the core purpose followed by the two pieces of differentiating information (Epic/relationship coverage, include-based enrichment). No filler or repetition of the title.

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 an output schema present, the description needn't explain return values, and annotations cover the read-only/idempotent profile; the description completes the picture by noting default Epic/relationship inclusion and enrichment options. Only a note on large-issue behavior or comment truncation would make it fuller.

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 eight parameters including expand, fields, include, properties and use_display_names are already documented in the schema. The description only restates the 'include' values that the schema already lists, adding no format, default or interaction guidance. Baseline 3 is appropriate when the schema carries the semantics.

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 and resource ('Get details of a specific Jira issue'), which is immediately distinguishable from siblings like jira_search or jira_update_issue. It also flags that Epic links and relationship data come back by default, which sharpens the scope. It does not explicitly name which sibling to use instead, keeping it at a 4 rather than a 5.

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?

Clear usage context is given: enrichments such as remote_links, transitions, watchers, changelog, comments and worklogs should be requested via 'include' rather than separate calls, which implicitly steers agents away from jira_get_issue_watchers / jira_get_worklog. No explicit when-not-to-use or prerequisites are stated, so it falls short of a 5.

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

Deploy Server

Other Tools