Skip to main content
Glama

render

Start exporting an MP4 of a film, scene, or shot, or WAV/MP3 audio, then poll status until complete to receive the file path.

Instructions

Start making a video file (MP4) of the film, one scene or one shot, the same way Export does. It returns at once; then call render_status until done (it gives the file path). Only one render runs at a time, and look doesn't work while it runs. quality draft is 540p and quick (for checking timing); final is full size and much slower. make wav or mp3 exports only the sound. Without save_to it goes to Dinoctor's renders folder. To stop it, use cancel_render.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoA scene id (what: scene) or shot id (what: shot).
fpsNo24, 30 or 60 (final only).
blurNoMotion blur for final (about 4 times slower). Default on where possible.
makeNoDefault video.
shotNoShot index in that scene, from 0.
sizeNoFinal only: picture size. Default 1080.
whatNoWhat to render. Default film.
sceneNoScene index from 0.
qualityNoDefault draft.
replaceNoWrite over save_to if it's already there.
save_toNoFull path of the file to make, ending in .mp4 (or .wav/.mp3). Ask the person where if they care.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / size / description
      Added value: +"Final only: picture size. Default 1080."
    • changedInput schema / properties / what / description
      Previous value: -"Default film."New value: +"What to render. Default film."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the asynchronous contract (returns at once, poll render_status for the file path), a global concurrency limit, the side effect that look is unavailable during a render, the performance tradeoff of draft vs final, and the default output location when save_to is omitted. These are exactly the behavioral facts an agent needs and none are in the annotation set.

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?

The verb and primary effect are front-loaded, and nearly every sentence carries distinct operational information (async flow, concurrency, quality, audio mode, default path, cancellation). It is densely packed into long comma-spliced clauses, which slightly reduces readability but wastes little.

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 an 11-parameter, zero-required mutation tool with no output schema, the description covers the lifecycle (start, poll, cancel), resource contention, quality/perf tradeoffs, and default destination. Nothing an agent needs in order to invoke it correctly and interpret the async result is missing.

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 100%, so the baseline is 3, but the description adds real meaning: quality=draft is 540p and fast while final is full-size and slow, make=wav/mp3 yields sound only, and omitting save_to routes output to Dinoctor's renders folder. It does not clarify id/shot/scene interplay or fps/size restrictions beyond the schema, keeping it from a 5.

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?

The description opens with a specific verb+resource ('Start making a video file (MP4)') and immediately bounds the scope to the film, one scene, or one shot. It explicitly distinguishes itself from Export, render_status, and cancel_render, so an agent can place it among siblings without opening a schema.

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?

It gives concrete follow-up routing ('call render_status until done', 'To stop it, use cancel_render') and decision guidance for draft vs final ('for checking timing' vs 'much slower') and for audio-only output via make wav/mp3. It stops short of an explicit when-not-to-use statement, but the concurrency constraint ('Only one render runs at a time') effectively frames the operating condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.