Skip to main content
Glama

Send a file from your computer

create_upload

A signed upload URL for a local file, and the file_url to use it For an agent that has a file on the person's computer but can only pass URLs (the CLI sends files itself): returns upload_url, where you PUT the file's bytes within an hour with the headers given, e.g. curl -X PUT -H "content-type: image/png" --upload-file desk.png "<upload_url>"; then pass file_url in any *_url field within a day: create_song (audio_url, cover_art_url), add_kit_piece (file_url), start_character (photo_urls), upload_background (file_url), set_artist_image (image_url). That field checks the file like an upload (format, size, rights) and keeps its own copy; this one is deleted after a day. size_bytes must be the file's exact size (up to 300 MB), content_type its type. Up to 100 files a day; without a plan, only a free song's audio and cover.

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": {
      "filename": "<filename>",
      "content_type": "<content_type>",
      "size_bytes": "<size_bytes>"
    },
    "name": "create_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesThe file's name, e.g. desk.png (kept on the stored copy)
size_bytesYesIts exact size in bytes (the upload must match it)
content_typeYesIts type: audio/mpeg, audio/wav, audio/mp4, image/jpeg, image/png, image/webp, video/mp4, video/quicktime or video/webm

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which only say this is not read-only, not destructive, not idempotent), the description discloses the two-stage lifecycle and expiries — PUT within an hour, redeem file_url within a day, the upload is deleted after a day while the consuming field keeps its own copy — plus the 100-files-per-day quota and plan gating. It even notes the consuming field re-validates format, size and rights.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: it leads with what is returned, then the PUT mechanics, then the redemption targets, then limits. Some clauses run together without punctuation ("...the file_url to use it For an agent...") and the example curl could be trimmed, but almost every sentence carries unique operational information.

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?

There is no output schema, so the description carries the return contract itself and does so fully (upload_url, file_url, required headers, expiry). For a three-parameter tool it leaves nothing an agent needs in order to complete the two-step upload and redemption.

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%, so the baseline is 3, but the description adds real meaning: size_bytes must be the file's exact size and the upload must match it, the 300 MB ceiling, and that filename is retained on the stored copy. The content_type guidance is largely a restatement of the enum.

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 a specific verb and resource (create a signed upload URL plus the file_url to redeem it) and immediately distinguishes this tool from the upload_* siblings by explaining it exists for agents that can only pass URLs. An agent can tell it apart from create_song/upload_background without inspecting schemas.

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?

It gives explicit when-to-use (file is on the person's computer but you can only pass URLs), the alternative it is not for (the CLI sends files itself), and a concrete routing table of which *_url field to pass the result into (audio_url, cover_art_url, file_url, photo_urls, image_url). The free-plan limitation is also spelled out.

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.

Resources