Skip to main content
Glama

render

Export your edited timeline to a video file, applying cuts, zooms, b-roll, music and captions in a single ffmpeg pass, or queue the export in Premiere or Resolve.

Instructions

Export the edited timeline to a file. Standalone: one ffmpeg pass with cuts, zooms, b-roll, music, captions, optional vertical reframe and loudness normalisation. Premiere/Resolve: queues the editor's own export (reframe/burnCaptions/loudnorm are standalone-only).

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": {
      "output": "<output>"
    },
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYesOutput path, e.g. ~/Movies/final.mp4
presetNoStandalone: x264 preset; Premiere: .epr preset path; Resolve: render preset name
reframeNoCentre-crop to this aspect (9:16 for Shorts/Reels/TikTok)
loudnormNoNormalise loudness to -14 LUFS
burnCaptionsNoBurn captions into the picture (default true when captions exist)

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?

With no annotations, the description carries the burden and does real work: it discloses the execution model (one ffmpeg pass vs. queuing the host editor's export), which options only apply standalone, and that reframe/loudnorm are optional. It does not say whether the call blocks until the file exists, whether it overwrites an existing output, or what happens to the queued host export.

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 core action, then split cleanly by execution mode. Every clause carries distinct information; no filler or restatement of the name.

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?

Strong for a 5-parameter tool with no output schema: it explains both execution paths and per-path parameter validity. The remaining gap is the return contract — whether the agent gets a path, a job handle, or an immediate queue acknowledgement — which matters especially for the asynchronous Premiere/Resolve path.

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 100%, so baseline would be 3, but the description adds genuine meaning beyond the schema by making the host-conditionality explicit: reframe, burnCaptions, and loudnorm only function in the standalone path, and 'preset' means different things per host. This is information an agent cannot derive from the schema alone.

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?

Names a specific verb (export/render) and a specific resource (the edited timeline to a file), and scopes it as the full-timeline export, which reads distinctly against siblings like render_caption_overlay or render_motion that act on components. An agent can tell what this produces without opening the 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?

Clearly frames host-dependent behavior: standalone does a single ffmpeg pass, while Premiere/Resolve queues the editor's own export. It also states which options are standalone-only, which tells the agent when certain parameters are meaningful. It stops short of naming an explicit alternative tool or an exclusion case.

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