Skip to main content
Glama

Begin a file upload

begin_asset_upload

Begin uploading a local media file, a data file (.json, .geojson, .topojson, .csv, .tsv or .svg, up to 2 MB) a component reads with , or a font file (.ttf, .otf, .woff or .woff2, up to 10 MB) whose family text then uses (guide/fonts). Supply filename, MIME type and byte size. Returns a new Asset ID for this upload and the upload command or commands. Run them from the agent machine, in order, then call complete_asset_upload. A file over 95 MB goes in parts: one command sends them all, and complete_asset_upload names any part still missing. Do not send bytes through tool arguments. If an upload command cannot connect (a proxy answers 403 or connect_rejected, the connection is refused, or the host name does not resolve), do not retry it. If you have the create_upload_link or upload_files tool, call it instead: it gives the person a link where they add the file from their device.

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>",
      "startSeconds": "<startSeconds>",
      "endSeconds": "<endSeconds>",
      "mimeType": "<mimeType>",
      "size": "<size>",
      "keepOriginal": "<keepOriginal>",
      "projectId": "<projectId>"
    },
    "name": "begin_asset_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
fileNameYes
mimeTypeYes
projectIdYesThe project this call runs on without changing the open project. null (or leaving it out) uses the open project. wait_for_jobs takes the projectId of the calls that started the jobs.
endSecondsYesVideo range end in source seconds. Both bounds are required for a range; the rest is discarded. Imported video starts at zero. Cannot combine with keepOriginal.
keepOriginalYesVideo only. null or false keeps one copy at up to 1080p, which both preview and export use. true also keeps the original file, and export uses it, so a 4K source exports at 4K. Default to null. Pass true only when the user asks to keep the original or export at full quality.
startSecondsYesVideo range start in source seconds. Use null with endSeconds null for the whole file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare the generic safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description carries the real burden and does: it states no bytes go through arguments, that it returns an Asset ID plus shell commands, size limits (2 MB data / 10 MB font / multi-part above 95 MB), and a non-retry failure policy. It does not state auth scope or what happens to a partially uploaded asset if complete_asset_upload is never called.

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?

Front-loaded with the core action and formats before the workflow and failure policy. The long parenthetical format lists are dense and one sentence spans several ideas, but no sentence is pure 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?

Covers the two-step upload protocol, return values (Asset ID + commands), size ceilings, and fallback routing, which is most of what an agent needs with no output schema. The notable omission is that the tool also accepts video with startSeconds/endSeconds trimming and keepOriginal, which the description never mentions.

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 57%; the description accounts for the three undocumented required fields (fileName, mimeType, size) by naming them as the supply set. It adds nothing about the video-range or keepOriginal parameters, but those are already explained in the schema, so the description and schema complement rather than overlap.

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?

Specific verb and resource: it begins an upload of a *local* file, and it enumerates the three categories (media, data file read with <prop data>, font file) with size caps. It is clearly separable from siblings like create_upload_link, upload_files, import_asset_url, and complete_asset_upload.

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?

Gives an explicit workflow (run the returned commands in order, then call complete_asset_upload), a part-upload rule for files over 95 MB, and hard exclusions: do not retry on proxy 403/connect_rejected/refused/unresolved host, and use create_upload_link or upload_files instead when available.

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.