Skip to main content
Glama

get_video_upload_url

Get a presigned URL to upload a video that only exists locally (not yet reachable at a public URL) so it can be scheduled.

schedule_reel, schedule_reels_bulk, and generate_reel_captions all need either a source_url (a link they can fetch from, e.g. Google Drive shared "Anyone with the link") or a video_token. When the video is just a local file with no public link, use this instead: PUT the raw video bytes directly to upload_url (as a plain HTTP PUT — do NOT route the bytes through this MCP connection, e.g. as a tool argument or base64; the upload_url accepts the request body as-is, with a Content-Type header matching the mime_type you passed here). Once that PUT succeeds, pass video_token to schedule_reel/schedule_reels_bulk/generate_reel_captions in place of source_url — it identifies the object you just uploaded, the same as a video_token generate_reel_captions returns.

upload_url expires in expires_in seconds — request a fresh one if the upload doesn't complete in time.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_video_upload_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
mime_typeNovideo/mp4
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
expires_inYes
upload_urlYes
video_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the expiry window (upload_url expires in expires_in seconds), the critical constraint that bytes must not be routed through the MCP connection as a tool argument or base64, and the Content-Type requirement. Missing only whether repeated calls create multiple orphaned objects or whether a prior token is invalidated.

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 purpose and the use-when condition, then operational steps, then the expiry caveat. The paragraph explaining that the token identifies the uploaded object partially repeats what was already said about passing video_token, which is the only real redundancy in an otherwise dense description.

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 two-step upload flow this covers everything an agent needs: when to call it, how to transfer bytes outside the MCP channel, the header constraint, the token handoff, and expiry behavior. An output schema exists, so return-value structure need not be re-explained.

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% for 2 params, so the description must compensate. It gives mime_type real meaning by tying it to the Content-Type header of the subsequent PUT and defaulting implicitly to video/mp4. workspace_id is never explained — presumably the target account — which is the one remaining gap.

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?

States a specific verb and resource (get a presigned upload URL), scoped precisely to 'a video that only exists locally (not yet reachable at a public URL)', and ties it to the downstream goal (so it can be scheduled). This makes it distinguishable from scheduling tools and from the sibling get_pdf_upload_url by media type.

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?

Explicitly names the three consumers (schedule_reel, schedule_reels_bulk, generate_reel_captions), states the condition that selects this tool (local file, no public link), and explains what those tools need instead (source_url or video_token). It also spells out the required follow-up: PUT the bytes, then pass the returned video_token in place of source_url.

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