Skip to main content
Glama

Finish a video upload

commit_upload

Step 3, after the PUT: checks the file and returns a source (status probing). Poll get_upload until ready, then start_swap, use_own_video or stitch_videos with its id.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "commit_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses that this call validates the uploaded file and only kicks off status probing rather than completing synchronously, requiring get_upload polling. That is real behavioral context the annotations don't convey. It is silent on re-invocation behavior for a tool marked non-idempotent and on what happens when the check fails.

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?

Two compact sentences, front-loaded with the pipeline step ("Step 3, after the PUT") so the agent gets position in the workflow immediately. The telegraphic style saves space but at the cost of some clarity around "returns a source."

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?

For a single-parameter tool with annotations present and no output schema, the description covers predecessor step, async polling requirement, and the three follow-on tools that consume the returned id — enough to drive correct invocation. Remaining gaps are upload_id provenance and failure/error semantics, which are moderate rather than blocking.

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 description coverage is 0%, so the description carries the burden for upload_id and only implicitly identifies it via "Step 3, after the PUT" and the later references to "its id." It never states that upload_id comes from create_upload/get_upload or how it differs from the returned source id, so a modest amount of meaning is added but the gap is not closed.

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?

The description gives a specific placement and action: "Step 3, after the PUT: checks the file and returns a source," which is clearly a finalize/verify step for a video upload. It separates itself from siblings by naming the preceding PUT and the downstream consumers, though the phrase "returns a source" is jargon that isn't unpacked.

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?

Explicit sequencing guidance: call this after the PUT, then "Poll get_upload until ready, then start_swap, use_own_video or stitch_videos with its id." That tells the agent both when to invoke and what to do next with the returned id. It does not state when not to use it or how to handle a failed check.

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.