Skip to main content
Glama

Get upload URLs

get_upload_urls

Creates presigned upload URL and file-path pairs for local media. Use when a generation needs a file the user has locally: upload raw bytes to the returned upload_url, then pass its file_path to the create tool. Does not upload file bytes or start a generation.

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": {
      "items": "<items>"
    },
    "name": "get_upload_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesThe list of assets to upload. The response array will match the order of items in the request body.

Output Schema

NameRequiredDescriptionDefault
itemsYesThe list of upload URLs and file paths for the assets. The response array will match the order of items in the request body. Refer to the [Input Files Guide](https://docs.magichour.ai/integration/inputs-and-outputs) for more details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the output is a URL/path pair, bytes are not sent here, and the path is the token to hand to a create tool. It omits how long a presigned URL stays valid, which matters for a non-idempotent URL-minting call.

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?

Three short sentences: identity of the tool, when to use it plus the workflow, then the boundary. The most decision-relevant content (what it creates) is front-loaded and no sentence is filler.

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?

With an output schema present, the description needn't explain return values, and it correctly focuses on the call sequence and the not-uploading caveat. For a URL-minting tool, the one meaningful omission is URL lifetime/expiry, which an agent would want before advising a user on a slow upload.

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% and the single `items` parameter is thoroughly documented in the schema itself, including type enum values, extension patterns, and the example array. The description adds nothing about batching, ordering, or per-item semantics beyond what the schema states, so the baseline 3 applies.

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?

"Creates presigned upload URL and file-path pairs for local media" gives a specific verb (creates), a specific resource (presigned upload URLs plus file paths), and a scope qualifier (local media). The closing sentence "Does not upload file bytes or start a generation" preempts the most likely confusion with the upload/create siblings, so an agent can place this tool correctly without opening a schema.

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?

"Use when a generation needs a file the user has locally" is an explicit trigger condition, and the description spells out the follow-on sequence: upload raw bytes to the returned upload_url, then pass its file_path to the create tool. It also states a negative case (does not upload bytes, does not start a generation). The only gap is that it never names which sibling to choose for the alternative paths, so it lands just below the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.