Skip to main content
Glama
asky74

mcp-server-atlassian-jira

by asky74
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Jira Get Attachment

jira_get_attachment
Read-only

Download a Jira attachment to a local file with or without a specified output path.

Instructions

Download a Jira attachment to a local file.

Usage:

jira_get_attachment({
  attachmentId: "12345",
  outputPath: "/tmp/report.pdf"  // optional
})

Parameters:

  • attachmentId (required): The attachment ID from issue metadata

  • outputPath (optional): Where to save the file. If not provided, saves to system temp directory with original filename.

To find attachment IDs: Use jira_get with:

  • path: /rest/api/3/issue/{issueKey}

  • jq: fields.attachment[*].{id:id,filename:filename,size:size}

Returns: Download result with file path, filename, MIME type, and size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputPathNoLocal file path where to save the attachment. If not provided, saves to system temp directory with original filename.
attachmentIdYesThe Jira attachment ID to download. Get this from issue metadata using jira_get with path "/rest/api/3/issue/{issueKey}" and jq "fields.attachment[*].{id:id,filename:filename}"

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true; description confirms download behavior. Discloses default save location (temp dir) and return fields. No contradiction with annotations.

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?

Structured with usage block, parameter list, tip, and return info. Length is justified by informative content; 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?

Covers: how to use, parameter defaults, prerequisite (finding IDs via sibling tool), and return values (file path, filename, MIME type, size). No output schema needed given description richness and annotations.

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%. Description adds usage example, explains default behavior for outputPath, and cross-references jira_get for attachmentId. Provides marginal additional value 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?

Clearly states 'Download a Jira attachment to a local file.' Differentiates from siblings: jira_get gets metadata, jira_attach uploads, etc. The verb 'download' and resource 'attachment' are specific and unambiguous.

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?

Provides explicit usage example and parameter details. Shows how to find attachment IDs via jira_get. Does not explicitly state when not to use, but context is sufficient for typical use.

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/asky74/mcp-server-atlassian-jira'

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