Skip to main content
Glama

jira_get_issue_images

Retrieve image attachments from a Jira issue as inline MCP image content using authenticated URLs; optionally fetch one specific attachment by ID.

Instructions

Get image attachments from a Jira issue as inline MCP image content. Uses Jira's authenticated attachment URLs, so the client does not need a separate browser login. Optionally provide an attachment ID to retrieve one specific image.

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_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYesIssue key (e.g., KP-123)
maxImagesNoMaximum images to return when attachmentId is omitted
attachmentIdNoSpecific attachment ID to retrieve (from jira_get_issue attachments)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description usefully discloses the auth model (Jira authenticated attachment URLs, no separate browser login needed) and the output modality (inline image content rather than URLs or metadata). It does not cover failure behavior — empty attachment lists, non-image attachments, or invalid attachment IDs — which is the main remaining gap for a bare, unannotated tool.

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 what is returned, then the auth rationale, then the optional narrowing parameter. Nothing is redundant and no sentence merely restates the tool name.

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?

For a 3-parameter read tool with no output schema and no annotations, the definition supplies the two things the schema cannot: what the response body actually is (inline image content) and how authentication is satisfied. Only error and empty-result behavior is unaddressed, which is a minor omission.

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 coverage is 100%, so issueKey, maxImages bounds/default, and attachmentId sourcing are already fully documented in the schema. The description restates the attachmentId option without adding format, validation, or ID-discovery detail beyond the schema's own pointer to jira_get_issue attachments.

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 image attachments from a Jira issue") plus the return channel (inline MCP image content), which immediately separates it from general issue readers like jira_get_issue. An agent can tell what it produces without opening the schema.

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 use of the optional attachmentId (fetch one specific image) versus the default bulk behavior is implied, and maxImages only matters when attachmentId is omitted. However, there is no explicit when-to-use framing, no stated exclusions, and no pointer to a sibling tool for the non-image case; usage is left to inference.

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