Skip to main content
Glama
GeiserX

atlassian-browser-mcp

by GeiserX
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Get Issue

jira_get_issue
Read-only

Retrieve detailed information for a specific Jira issue, including Epic links and relationship data. Supports custom fields, comments, and history updates.

Instructions

Get details of a specific Jira issue including its Epic links and relationship information.

Args: ctx: The FastMCP context. issue_key: Jira issue key. fields: Comma-separated list of fields to return (e.g., 'summary,status,customfield_10010'), a single field as a string (e.g., 'duedate'), '*all' for all fields, or omitted for essentials. expand: Optional fields to expand. comment_limit: Maximum number of comments. properties: Issue properties to return. update_history: Whether to update issue view history.

Returns: JSON string representing the Jira issue object.

Raises: ValueError: If the Jira client is not configured or available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_keyYesJira issue key (e.g., 'PROJ-123', 'ACV2-642')
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.reporter,status,priority,created,issuetype,summary,updated,labels,description,assignee
expandNo(Optional) Fields to expand. Examples: 'renderedFields' (for rendered content), 'transitions' (for available status transitions), 'changelog' (for history)
comment_limitNoMaximum number of comments to include (0 or null for no comments)
propertiesNo(Optional) A comma-separated list of issue properties to return
update_historyNoWhether to update the issue view history for the requesting user

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true, and the description adds behavioral details: raises ValueError if Jira client not configured, and includes update_history parameter that modifies view history. This adds value beyond annotations.

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?

Description is well-structured with clear Args, Returns, Raises sections. First sentence delivers purpose immediately. Every sentence earns its place; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists and parameters are fully described, the description is complete. It covers return format, error cases, and parameter options comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds context for fields (e.g., '*all', single string, omitted for essentials) and expand (examples: 'renderedFields', 'transitions'), enhancing understanding beyond schema.

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?

The description clearly states 'Get details of a specific Jira issue including its Epic links and relationship information.' It uses a specific verb and resource, and distinguishes from sibling tools like jira_search or jira_get_project_issues.

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?

The description implies usage through mention of 'Epic links and relationship information' but does not explicitly state when to use this tool versus alternatives like jira_search or jira_get_project_issues. No exclusions or when-not-to-use guidance.

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/GeiserX/atlassian-browser-mcp'

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