Skip to main content
Glama
SharkyND

mcp-atlassian

by SharkyND
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

jira_download_attachments

Download attachments from a Jira issue to disk or cache as MCP resources for immediate access via static URIs.

Instructions

Download attachments from a Jira issue to disk, MCP resources, or both.

When resource caching is enabled, each attachment is immediately available in the MCP resource browser via a static URI — no cache key required:

jira://attachments/{issue_key}/{filename}

Examples: jira://attachments/JDQU-2322/desktop-screenshot-1.png ← renders as image jira://attachments/JDQU-2322/SPyDR%20Metadata.txt ← opens as text

Cached resources are valid for 10 minutes. Re-run this tool to refresh.

Args: ctx: The FastMCP context. issue_key: Jira issue key (e.g., 'PROJ-123'). target_dir: Optional server-side save path for downloaded files. return_content: Optional flag to cache attachments as MCP resources.

Returns: JSON string with download results. Attachments may include: - filename: The attachment filename - size: File size in bytes - path: Server-side download path when target_dir is provided - static_resource_uri: Direct MCP resource URI when return_content is enabled - mime_type: MIME type of the file when return_content is enabled

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_keyYesJira issue key (e.g., 'PROJ-123')
target_dirNo(Optional) Directory where attachments should be saved on the server. Preserves the legacy jira_download_attachments behavior.
return_contentNo(Optional) Cache attachments as MCP resources. Defaults to true when target_dir is omitted and false when target_dir is provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

With no annotations, the description fully discloses caching behavior, URI format, 10-minute validity, and default parameter interactions. It does not explicitly mention read-only nature or authentication.

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?

The description is well-organized with clear sections (purpose, caching, examples, args, returns). Every sentence serves a purpose, and the most critical information is front-loaded.

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 the tool's moderate complexity and the presence of an output schema, the description thoroughly covers all aspects: inputs, outputs, caching behavior, default logic, and resource URI format.

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

Parameters5/5

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

The description adds substantial meaning beyond the schema, including dynamic default rules for return_content, MCP resource URI examples, and explanations of how parameters affect behavior.

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 states 'Download attachments from a Jira issue to disk, MCP resources, or both.' This is a specific verb-resource pair with clear scope, distinguishing it from upload and listing tools.

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 explains the caching mechanism and default behavior but does not explicitly guide when to use this tool versus siblings like jira_list_cached_attachments or jira_save_attachment_to_disk.

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

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