Skip to main content
Glama
Sign In
namcpgem

Jira MCP

by namcpgem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_ticket

Retrieve full details of a Jira ticket by key, optionally including comments, worklogs, and image attachments. Use it to inspect a single issue before acting or updating.

Instructions

Get full details of a Jira ticket by its key. For a single comment (a ?focusedCommentId= link), use get_comment instead.

Input Schema

NameRequiredDescriptionDefault
ticket_idYesJira issue key, e.g. GEM-234
image_limitNoMax images to return with include_images (default 5, max 20); the total size cap still applies
include_imagesNoReturn image attachments (screenshots referenced as !name.png! in the description/comments) as viewable images (default false)
include_commentsNoInclude the ticket's comments (default false)
include_worklogsNoInclude the ticket's worklogs with their IDs (default false, one extra request)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.7.0
    • addedInput schema / properties / include_worklogs
      Added value: +{
+  "description": "Include the ticket's worklogs with their IDs (default false, one extra request)",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv2.6.0
    • addedInput schema / properties / image_limit
      Added value: +{
+  "description": "Max images to return with include_images (default 5, max 20); the total size cap still applies",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / include_images
      Added value: +{
+  "description": "Return image attachments (screenshots referenced as !name.png! in the description/comments) as viewable images (default false)",
+  "type": "boolean"
+}
  3. Changed1 schema field changedv2.2.0
    • addedInput schema / properties / include_comments
      Added value: +{
+  "description": "Include the ticket's comments (default false)",
+  "type": "boolean"
+}
  4. First observedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It correctly implies a safe read ('Get full details') but says nothing about what happens with an unknown key, permission requirements, or that comments/worklogs/images are excluded unless toggled on and that include_worklogs costs an extra request — that cost signal lives only in the schema.

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 waste, with the primary action front-loaded and the disambiguation clause second. Every sentence earns its place.

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?

There is no output schema, but the description plus the fully-covered input schema tell the agent how to shape the response via the include_* toggles. Missing only a note on error behavior for invalid keys and the fact that the default response omits comments/worklogs, which an agent could easily misread as 'full details' includes everything.

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 parameters (ticket_id, include_images, image_limit, include_comments, include_worklogs) are already fully documented with defaults and caps. The description adds only the general notion that the response is the 'full details' of the keyed ticket, no format or behavior detail beyond the schema. 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?

States a specific verb and resource ('Get full details of a Jira ticket by its key') and immediately contrasts with the sibling get_comment. An agent can tell get_ticket apart from get_comment, search_tickets, and update_ticket without opening any schema.

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?

Explicitly routes the single-comment case (a ?focusedCommentId= link) to get_comment, which is a concrete when-not-to-use rule. It does not address the search_tickets relationship (find a key vs. fetch by key), so guidance is clear but not exhaustive.

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