Skip to main content
Glama

Revise a video

revise_video

Change a ready video with a note, e.g. "make the headline shorter" or "use a darker background in the last scene". The earlier cut is kept as a version. The first three changes to a video are included, then each counts as one video; poll get_video until revising is false.

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": {
      "id": "<id>",
      "note": "<note>"
    },
    "name": "revise_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoOptional second in the video the note is about.
idYesThe video id from create_video or list_videos.
noteYesWhat to change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the prior cut is preserved as a version (changes are non-destructive/reversible), that the operation is asynchronous via a 'revising' flag, and that the first three revisions are free while later ones bill as one video each. It stops short of stating failure modes, whether the video must be in a specific state, or what the response body contains.

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?

Three tight sentences, front-loaded with the action and examples, followed by the versioning/cost consequence and the polling instruction. Every sentence carries distinct information; nothing is redundant.

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 an async, billed mutation with no annotations and no output schema, the description supplies the essentials: versioning, cost model, and the polling loop. Only error/edge-case behavior (invalid note, non-ready video) is unaddressed.

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 id, note, and at are already documented. The description's example notes add real meaning about how to phrase the note parameter, but it says nothing about the optional 'at' second marker or its interaction with the note. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ("Change a ready video") and reinforces it with two concrete example notes, so the agent knows this edits an existing rendered video rather than producing a new one. It does not explicitly name create_video/list_videos as the alternatives, but "ready video" plus the id source in the schema makes the distinction legible.

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 a clear invocation workflow — call it, then poll get_video until revising is false — which is the key when-to-use guidance for an async mutation. It lacks explicit when-not-to-use guidance (e.g., video not yet ready, or wanting a fresh generation via create_video instead of a revision).

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