Skip to main content
Glama

render

Creates AI video clips from a text prompt or source image, with optional model, style, quality, camera, speed, and timing controls; returns a job ID for status tracking.

Instructions

Makes a video from a prompt, starting from a picture (image = a name from upload_image) or, with no image, from the prompt alone (text to video: describe the whole scene). Everything else is optional: model: small (default, fast) | ltx13 | vace | an added model's file name (list_models) style: e.g. "Balanced", "Soft and calm", "Lively", "Slow motion" (render_options lists all) quality: "Draft" (fastest) | "Normal" (default) | "High" | "Best" (1080p, very slow) | "Manual" (then width, height) seconds: 1-7 (2-3 holds together best). camera: still | zoom | zoomout | panr | panl. speed: slow | normal | fast movement: 10-70, how much things move (style sets it). seed: -1 = new each time; same seed + settings = same video. avoid: what must not appear (vace and LTX dev models only). priority: "user" (default, goes first) or "batch" (waits while the user's own renders go first). Returns a job id right away; then call job_status(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": {
      "prompt": "<prompt>"
    },
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNo
avoidNo
imageNo
modelNo
speedNo
styleNo
widthNo
cameraNo
heightNo
promptYes
qualityNo
secondsNo
movementNo
priorityNouser

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-destructive, closed-world write. The description adds meaningful behavior beyond that: the call returns a job id immediately and requires a follow-up job_status(id), priority "user" jumps ahead of "batch", same seed plus same settings reproduces a video, and avoid only works on vace and LTX dev models. It says nothing about cost or queuing limits, which would round this out.

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 the core action and mode split, then a compact parameter glossary with no filler sentences. It is dense and slightly run-on because of the inline enumerations, but each clause conveys information an agent needs for this 14-parameter tool.

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?

Covers the full call cycle: what goes in, the optional knobs, and the fact that a job id comes back immediately and must be polled with job_status. With no output schema, more explicit return-value detail would help, but the async contract and all parameters are documented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 14 parameters, so the description carries the full burden, and it does: image, model, style, quality, width/height (via "Manual"), seconds range, camera values, speed values, movement range, seed semantics, avoid restrictions, and priority are all explained inline. The only thin spot is prompt itself, whose meaning is only implied by "describe the whole scene."

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 ("Makes a video from a prompt") and immediately splits the two modes: image-to-video where image is a name from upload_image, or text-to-video where the prompt must describe the whole scene. That is enough for an agent to distinguish render from render_batch or render_variations.

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?

Explains how each optional parameter steers the result (e.g. quality "Draft" fastest, "Best" 1080p very slow, seconds 2-3 holds together best, style sets movement) and routes to render_options and list_models for the enumerations it does not inline. It does not explicitly say when to prefer a sibling like render_variations or render_batch, so it stops short of full when/when-not guidance.

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