Skip to main content
Glama

Review a render

review_render
Read-only

Everything needed to check a finished render in one call: contact sheets of every frame (each stamped with its frame number), close-ups of the captions at every change (three frames in a row, to catch a blank or doubled caption), the end card, and a chart of the audio level with where the voice ends, the end card starts and the music fades, plus the level of each part. Returns the pictures inline with how to read each. 5 credits. It looks at up to 2 minutes at a time: review a longer video (a long-form export) in stretches with from_seconds and to_seconds, and the result says where the next stretch starts. For a long export's graphics and still images, around_graphics looks at three frames of each (just after it appears, once it has built or in its middle, just before it goes) in one call, however long the video. A long render can take a minute: if it says running, call again with the same arguments.

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": {
      "render_id": "<render_id>"
    },
    "name": "review_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
imagesNoSend the pictures inline; false gives their links only
render_idYes
to_secondsNoEnd of the stretch, at most 2 minutes after from_seconds and no later than the video's end
from_secondsNoStart of the stretch to review, in the video's seconds; give to_seconds too. Leave both out for the whole video (up to 2 minutes)
around_graphicsNoInstead of every frame: three frames of each graphic and still image of a long export, one a row, however long the video. Not with from_seconds and to_seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / around_graphics / description
      Previous value: -"Instead of every frame: three frames of each graphic of a long export, one graphic a row, however long the video. Not with from_seconds and to_seconds"New value: +"Instead of every frame: three frames of each graphic and still image of a long export, one a row, however long the video. Not with from_seconds and to_seconds"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does so well: it discloses the 5-credit cost, a 2-minute scope limit per call, and the asynchronous pattern that a long render may return 'running' and must be re-polled with the same arguments. Those are exactly the facts an agent needs and cannot get from the annotation.

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?

Content is front-loaded with the payoff (what you get back) before the operational rules, and every clause carries information. It runs long and repeats the 2-minute cap that the schema already states, costing it a point, but nothing is padding.

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?

No output schema exists, so the description must explain the return — and it does, describing the returned pictures, the reading instructions bundled with them, and the next-stretch marker. With a 5-parameter tool and thin annotations, all significant gaps are covered.

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 description coverage is already 80%, so baseline is 3; the description adds real meaning on top by explaining that from_seconds/to_seconds split a long render into stretches and that the result reports where the next stretch begins, and by defining around_graphics as three frames per graphic (just after it appears, once built, just before it goes). The images parameter is left to the schema.

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 ('check a finished render') and enumerates exactly what the call returns: contact sheets stamped with frame numbers, caption close-ups at each change, the end card, and an audio-level chart with voice-end/end-card/music-fade markers. This is far more specific than the title and distinguishes it from a single-frame reviewer like review_shot.

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 clear when-to-use context and routing rules: use from_seconds/to_seconds for videos past 2 minutes, use around_graphics instead of every frame for a long export's graphics and stills, and re-call with identical arguments if the result says running. It stops short of naming sibling tools (e.g. review_shot, get_render), so the agent must infer when this beats those, but the internal alternatives are spelled out.

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