Skip to main content
Glama

Render a video

render
Idempotent

Render a video. source: files (name: text) or url (https zip) plus entry. hyperframes: index.html; data-composition-id, data-start, data-duration, data-track-index; paused window.__timelines[id]; no clock/fetch. shader: main.frag (GLSL 450; set 0 binding 0 uniform: float time, frame; vec2 resolution), .wgsl/.slang. Shadertoy works; no iChannel/iMouse/sound. blender: scene.py or main.blend. mitsuba: scene.xml, cuda_ad_rgb. composite: graph.json layers [{media_url,start_s,end_s}]. film: project_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": {
      "source": "<source>"
    },
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNoSize, codec, quality.
sourceYesSource.
wait_sNoMax 50s.
dry_runNoPrice only.
max_usdNoSpend cap, dollars.
idempotency_keyNoRetry key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Same request, same job."New value: +"Retry key."
    • changedInput schema / properties / source / description
      Previous value: -"What to render."New value: +"Source."
    • changedInput schema / properties / wait_s / description
      Previous value: -"Seconds to wait, at most 50."New value: +"Max 50s."
  2. Changed5 schema fields changed
    • changedInput schema / properties / dry_run / description
      Previous value: -"Price it and start nothing."New value: +"Price only."
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Reuse this on retry."New value: +"Same request, same job."
    • changedInput schema / properties / max_usd / description
      Previous value: -"Most to spend, in dollars."New value: +"Spend cap, dollars."
    • changedInput schema / properties / out / description
      Previous value: -"Size, speed, codec and quality. Times are seconds."New value: +"Size, codec, quality."
    • changedInput schema / properties / wait_s / description
      Previous value: -"Wait this many seconds. At most 50."New value: +"Seconds to wait, at most 50."
  3. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, open-world, idempotent, non-destructive operation. The description adds useful source-specific constraints, such as hyperframes having no clock/fetch and shader sources lacking iChannel/iMouse/sound, but it omits async/job behavior, cost implications, and return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and compact, but it is a dense semicolon-separated block that is cryptic to read. It avoids waste but sacrifices structure and clarity for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex render tool with nested source parameters and no output schema, so the description should explain return values or job behavior. It covers source specification well but leaves out what the call returns, how rendering is tracked, and how wait_s, dry_run, max_usd, and idempotency_key affect operation beyond their schema descriptions.

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 meaning beyond the schema by explaining what files, url, and entry mean for each source kind. It clarifies hyperframes, shader, blender, mitsuba, composite, and film source requirements in a way the schema alone does not.

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 states a specific verb and resource: "Render a video." It is clear what the tool does, but it does not explicitly distinguish this tool from siblings such as render_frames or render_job.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains how to specify different source kinds but gives no explicit when-to-use or when-not-to-use guidance. It does not name alternatives or clarify why an agent should choose this render tool over related render/job tools.

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