Skip to main content
Glama
asky74

mcp-server-atlassian-jira

by asky74

Jira Attach File

jira_attach
Read-only

Upload a file or text content as an attachment to a specified Jira issue. Supports images, documents, archives, and code files.

Instructions

Upload a file attachment to a Jira issue.

Two ways to attach files:

  1. Local file: Provide filePath to upload an existing file

    jira_attach({
      issueIdOrKey: "PROJ-123",
      filePath: "/path/to/screenshot.png"
    })
  2. Text content: Provide textContent and fileName to create and upload a text file

    jira_attach({
      issueIdOrKey: "PROJ-123",
      textContent: "Error log contents here...",
      fileName: "error.log"
    })

Supported file types: Images (png, jpg, gif), documents (pdf, doc, xls), text (txt, csv, json, md, log), archives (zip, tar), code files, and more.

Returns: Attachment metadata including ID, filename, size, and URL.

To list existing attachments: Use jira_get with:

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNameNoFilename to use when uploading textContent (e.g., "notes.txt", "report.md")
filePathNoPath to the local file to upload. Use this OR textContent/fileName, not both.
textContentNoText content to upload as a file. Requires fileName to be specified.
issueIdOrKeyYesThe Jira issue ID or key to attach the file to (e.g., "PROJ-123" or "10001")
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description describes a write operation ('upload'). This is a direct contradiction. Beyond that, the description adds useful behavioral context (supported file types, returns metadata), but the contradiction is critical.

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 sections, bullet points, and code blocks. Every sentence serves a purpose, no fluff. It is concise yet comprehensive.

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?

Despite the annotation contradiction, the description covers the two attachment methods, supported file types, and return metadata. It lacks permission or size limit info, but is generally complete for the task.

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%, but the description adds significant meaning: explains mutual exclusivity of filePath vs textContent/fileName, provides example values, and clarifies the required relationship between textContent and fileName.

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 'Upload a file attachment to a Jira issue' with specific verb and resource. It distinguishes from sibling tools like jira_get_attachment and provides two concrete usage modes with examples.

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?

The description explicitly details two ways to attach files and the required parameters. It also directs users to jira_get for listing attachments, guiding usage context. Could mention when not to use, but it's effective.

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