Skip to main content
Glama

upload_media_base64

Upload a local image, video, or audio file into Sequencer by passing base64 file contents. This is the MCP-native local-file path when the client can read the file bytes. For large videos, prefer the REST /v1/upload multipart endpoint to avoid MCP payload limits.

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": {
      "workspaceId": "<workspaceId>",
      "fileName": "<fileName>",
      "mimeType": "<mimeType>",
      "base64Data": "<base64Data>"
    },
    "name": "upload_media_base64"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNameYesOriginal file name, e.g. idle_loop_silent.mp4
folderIdNoOptional destination folder ID
mimeTypeYesMIME type, e.g. video/mp4
base64DataYesBase64-encoded file contents. Data URL prefixes are accepted.
workspaceIdYesThe workspace ID
idempotencyKeyNoStable upload/import key. Repeating the same bytes returns the original media without overwriting edits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "description": "Stable upload/import key. Repeating the same bytes returns the original media without overwriting edits.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does contribute the payload-size limitation and the local-file precondition. It omits what happens after upload (return value, whether processing is async and needs get_media_statuses polling) and any auth or error behavior, which matters for a write tool with no output schema.

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?

Two sentences, both earning their place: the first states what the tool does and its precondition, the second handles the large-file routing case. Nothing is padded or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation with no annotations and no output schema, the definition stops short of describing the response or follow-up status checks, which the presence of get_media_statuses suggests are relevant. Core invocation details are covered, but post-upload behavior is left to inference.

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 coverage is 100%, so parameter documentation already exists for all six fields, including idempotencyKey semantics and folderId. The description adds no meaning beyond the schema, restating only that contents are base64, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Upload a local image, video, or audio file into Sequencer by passing base64 file contents") and qualifies the path as the MCP-native local-file route. It does not explicitly contrast with sibling alternatives such as import_media_from_url, so an agent must infer that URL-based imports go elsewhere.

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?

Gives an explicit condition ("when the client can read the file bytes") plus an exclusion with a concrete reason: prefer the REST multipart endpoint for large videos to avoid MCP payload limits. That is strong routing guidance, though it points at a non-MCP endpoint rather than naming the sibling tool for remote-file imports.

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.