Skip to main content
Glama

jira_construct_upload_endpoint

Get upload URL and session token to upload local files, enabling attachment uploads to Jira via a two-step client-side flow.

Instructions

Return the URL and session token needed to upload local files to the MCP server.

This is step 1 of the client-side file upload flow:

  1. Call this tool to get upload_url + session_id.

  2. POST your file(s) to upload_url using multipart/form-data with the Mcp-Session-Id header set to session_id.

    Windows PowerShell (handles paths with spaces): curl.exe -X POST -H "Mcp-Session-Id: " -F 'file=@"C:\path with spaces\file.pdf"'

    Linux / macOS (handles paths with spaces): curl -X POST -H "Mcp-Session-Id: " -F "file=@'/path/with spaces/file.pdf'"

    The server returns: {"uploaded": [{"filename": "...", "uri": "upload://...", "size": ...}]}

  3. Pass the returned upload:// URIs to jira_upload_attachment.

Sessions expire after 30 minutes (configurable via UPLOAD_STAGING_TTL_MINUTES). The base URL defaults to http://localhost:8932 and can be overridden by the MCP_SERVER_BASE_URL environment variable.

Args: ctx: The FastMCP context.

Returns: JSON string with upload_url, session_id, required_headers, and OS-specific usage example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description carries full burden. It discloses key behavioral traits: session expiration ('Sessions expire after 30 minutes'), configurability of TTL and base URL, and the exact return structure including required_headers and usage example. This exceeds the basic expectations and provides transparency about operational constraints.

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 long but every sentence adds value. It is structured with a numbered flow, code samples, environment variable notes, and return format. The front-loaded purpose is immediately clear, and the details are organized logically. Nothing feels redundant.

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?

The description is fully complete for this tool's complexity. It explains the entire upload flow, session mechanics, configuration options, return values, and how to use the results with a sibling tool. Even though an output schema exists, the description already provides a precise return shape, making the tool independently understandable.

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?

The tool has 0 parameters, so the baseline is 4. The description mentions 'Args: ctx: The FastMCP context' but this is internal and not in the schema. The description adds no parameter semantics because there are none, but it does add value by documenting the return object and usage flow, covering any ambiguity.

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 the tool's purpose explicitly: 'Return the URL and session token needed to upload local files to the MCP server.' It uses a specific verb ('return') and resource (upload endpoint/session token), and clearly distinguishes itself from siblings like jira_construct_download_endpoint by focusing on uploads and describing the upload flow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit step-by-step usage instructions and names the alternative/next tool: 'This is step 1 of the client-side file upload flow' and 'Pass the returned upload:// URIs to jira_upload_attachment.' It also includes OS-specific curl examples, making it clear when and how to use the tool.

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