Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Attach a file

jira_add_attachment

Attach a file to a Jira issue by downloading it from a public URL or reading it from a local path on the server, with optional filename override.

Instructions

Attach a file to an issue, either downloaded from a public URL or read from a local path on the machine running this server.

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": {
      "issue": "<issue>"
    },
    "name": "jira_add_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic http(s) URL to download.
issueYesIssue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123').
filePathNoAbsolute path of a local file.
filenameNoOverride the attachment file name.
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds one genuinely non-obvious behavior beyond that: local files are read from the filesystem of the machine running the server, which matters for path choice. It still says nothing about size caps, duplicate-filename handling, or whether attaching is idempotent, so it does not earn a 4.

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?

A single sentence, front-loaded with the action and resource, followed by the source modes. There is no filler, no restatement of the tool name, and nothing that could be trimmed without losing information.

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 five-parameter write tool with full schema coverage and no output schema, the description covers the essentials: the action, the two input modes, and the server-side read location. Only permission requirements and any failure conditions are absent, which are reasonable omissions given the annotations and schema carry the rest.

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 url, issue, filePath, filename and instance are all documented in the schema and the baseline is 3. The only semantic value added is the implicit mutual exclusivity of url and filePath ("either...or"), which the schema does not enforce, since only issue is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb with a specific resource ("attach a file to an issue") and enumerates the two supported sources, so an agent immediately knows what the tool accomplishes. It does not name a sibling or explicitly say what it is not, which keeps it just short of a 5.

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 "either downloaded from a public URL or read from a local path" phrasing implies the two usage contexts, which is real if modest guidance. There is no statement of prerequisites (attachment permissions, file-size limits), no when-not-to-use condition, and no pointer to an alternative tool, leaving usage largely inferred from the description.

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