Skip to main content
Glama

Upload asset

upload_asset

Upload a reference image, start frame, video or audio file and get an asset id to pass as inputs ({slot: [asset ids]}; slot names come from list_capabilities). Give exactly one of: path (a local file; only when the server runs locally over stdio), url (a public http(s) URL the server fetches), or data_base64 (with filename or content_type; up to 20 MB when the server is remote). data_base64 has to fit in the tool call itself, so it suits small files; for anything over a few hundred KB pass a url instead. Accepted: PNG, JPEG, WebP images (up to 20 MB); MP4, MOV, WebM video (200 MB, 60 s); MP3, WAV, M4A, OGG audio (25 MB, 5 min). The API detects the format from the bytes. Uploads are free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upload_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
pathNo
projectNo
filenameNo
data_base64No
content_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the mutation/open-world profile; the description adds substantive behavior: per-format size and duration ceilings, byte-level format detection, the 20 MB cap for remote base64, and that uploads are free. These constraints directly affect whether a call will succeed.

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 states the action and return value first, then the source-selection rule, then format limits. Most sentences carry load-bearing constraints, though the hard line breaks fall mid-sentence and could be tightened.

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?

For a six-parameter mutation tool with no schema documentation, the definition covers source selection, size/format limits, and the downstream use of the returned id; the output schema handles the return shape. Only the `project` parameter's role is unaddressed.

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 0%, so the description carries the burden, and it does: it defines `path`, `url`, `data_base64`, and the coupling of `filename`/`content_type` to base64, plus the exactly-one-of constraint. The `project` parameter is never mentioned, leaving one of six params unexplained.

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 names a specific verb (upload) and set of resources (reference image, start frame, video, audio) and states the concrete outcome: an asset id to pass as `inputs`. It is clearly distinct from the read-side siblings such as list_assets and download_asset.

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?

It gives explicit selection rules among the three sourcing modes: `path` only when the server runs locally over stdio, `url` for anything over a few hundred KB, `data_base64` for small inline payloads. It also points to list_capabilities for slot names. It stops short of naming tool-level alternatives, but the operational guidance is strong.

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