Skip to main content
Glama

var2_render_timeline

Build a PRECISE multi-track video timeline — explicit per-clip start times, overlaps, per-clip mute/volume/fades/trim, TEXT/CAPTION overlays with styling, audio tracks with offsets, and MOTION-GRAPHICS pieces as transparent overlays on top of the video (lower thirds, titles, end cards: a "motion" track) — and save it as an editable project (render=false, default) or queue the render (render=true). Accepts a simplified tracks[] or the raw GUI editor schema; captions turns word/line lyrics timestamps into a styled caption track server-side. Frames at 30fps are canonical; seconds fields are converted exactly. For simple back-to-back concatenation use var2_join_videos instead; status of a queued render → var2_check_join_status.

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": "var2_render_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
assetsNoRaw-schema mode: map of assetId → url / var2 share link / placeholder_id.
renderNoDefault false = save project only (user edits in GUI). true = also queue the render now.
schemaNoRAW GUI editor ProjectSchema passthrough (fps/width/height/durationInFrames/tracks with startFrame+durationInFrames). Use with `assets`. A motion clip here is {type: "motion", motion: <full Motion Spec, with overlay: true to composite over the tracks below>, startFrame, durationInFrames, trimStart, style} on a track of type "motion"; prefer the simplified tracks[] form, which resolves project_id for you.
tracksNoSimplified timeline: [{type: video|image|audio|text|motion, muted?, clips: [{type?, asset? (url/share link/placeholder_id), text? (string or {content,fontSize,color,backgroundColor,alignment,bold}), start_seconds?, duration_seconds (required, except motion), trim_start_seconds?, muted?, volume?, fade_in_seconds?, fade_out_seconds?, label?, objectFit?}]}]. Omitted start_seconds appends after the previous clip in the track. MOTION GRAPHICS ON TOP OF VIDEO: a track of type "motion" (put it AFTER the video tracks — later tracks draw on top) with clips {project_id (a saved piece from var2_create_motion_graphics / var2_save_motion_graphics) | spec (inline Motion Spec), start_seconds, duration_seconds? (default: the piece's length; never longer), trim_start_seconds?, overlay? (default true: the piece's background is dropped so the video shows through; false keeps it opaque), opacity? (0–1), fade_in_seconds?, fade_out_seconds?, x?, y? (centre in % of the canvas, default 50/50), scale? (0.05–1 of the canvas, default 1), include_audio? (default false: also add the piece's own voice-over / music)}. The piece is fitted without stretching whatever its aspect ratio, is read fresh from project_id on every call (edit the piece, call again, the new version renders), and each piece may be up to 60 s while the timeline may be 10 min.
captionsNoServer-computed caption/lyrics track — no frame math needed: {timestamps: [{text, start_seconds, end_seconds}] (word- OR line-level), max_words_per_caption? (word-level, default 4), style? (TextProps overrides), position? (bottom|top|center)}. Appended as a text track to the timeline.
resolutionNoDefault 1080p (render only).
aspect_ratioNoDefault 16:9.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / schema / description
      Previous value: -"RAW GUI editor ProjectSchema passthrough (fps/width/height/durationInFrames/tracks with startFrame+durationInFrames). Use with `assets`."New value: +"RAW GUI editor ProjectSchema passthrough (fps/width/height/durationInFrames/tracks with startFrame+durationInFrames). Use with `assets`. A motion clip here is {type: \"motion\", motion: <full Motion Spec, with overlay: true to composite over the tracks below>, startFrame, durationInFrames, trimStart, style} on a track of type \"motion\"; prefer the simplified tracks[] form, which resolves project_id for you."
    • changedInput schema / properties / tracks / description
      Previous value: -"Simplified timeline: [{type: video|image|audio|text, muted?, clips: [{type?, asset? (url/share link/placeholder_id), text? (string or {content,fontSize,color,backgroundColor,alignment,bold}), start_seconds?, duration_seconds (required), trim_start_seconds?, muted?, volume?, fade_in_seconds?, fade_out_seconds?, label?, objectFit?}]}]. Omitted start_seconds appends after the previous clip in the track."New value: +"Simplified timeline: [{type: video|image|audio|text|motion, muted?, clips: [{type?, asset? (url/share link/placeholder_id), text? (string or {content,fontSize,color,backgroundColor,alignment,bold}), start_seconds?, duration_seconds (required, except motion), trim_start_seconds?, muted?, volume?, fade_in_seconds?, fade_out_seconds?, label?, objectFit?}]}]. Omitted start_seconds appends after the previous clip in the track. MOTION GRAPHICS ON TOP OF VIDEO: a track of type \"motion\" (put it AFTER the video tracks — later tracks draw on top) with clips {project_id (a saved piece from var2_create_motion_graphics / var2_save_motion_graphics) | spec (inline Motion Spec), start_seconds, duration_seconds? (default: the piece's length; never longer), trim_start_seconds?, overlay? (default true: the piece's background is dropped so the video shows through; false keeps it opaque), opacity? (0–1), fade_in_seconds?, fade_out_seconds?, x?, y? (centre in % of the canvas, default 50/50), scale? (0.05–1 of the canvas, default 1), include_audio? (default false: also add the piece's own voice-over / music)}. The piece is fitted without stretching whatever its aspect ratio, is read fresh from project_id on every call (edit the piece, call again, the new version renders), and each piece may be up to 60 s while the timeline may be 10 min."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations carry only a title, so the description bears the full disclosure burden and does so: default is a saved editable project, render=true mutates state by queuing a render, motion pieces are re-read from project_id on every call, overlay=true drops the piece's background, later tracks draw on top, and hard limits (60 s per piece, 10 min timeline, 8 tracks). Those are exactly the operational facts an agent needs before invoking.

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?

Purpose, mode split, and sibling routing are front-loaded in the first two sentences, which is good structure. It is long and capitalization-heavy, though, and several clauses (motion clip field lists, overlay defaults) restate the input schema almost verbatim rather than adding new information.

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 8-parameter tool with nested objects, no output schema, and essentially empty annotations, the description covers inputs, defaults, ordering rules, size limits, and result retrieval. Nothing an agent needs to call this correctly appears to be 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 already 88%, so baseline is 3; the description still adds cross-parameter semantics the schema lacks, such as omitted start_seconds appending after the previous clip, frames at 30fps being canonical with exact seconds conversion, and track ordering determining z-order. It largely duplicates the schema's own tracks/motion prose, which keeps 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 ('Build a PRECISE multi-track video timeline') and enumerates the exact capabilities: per-clip timing, audio, text/caption overlays, and motion-graphics overlays. It also names the two closest siblings and the conditions separating them, so an agent can distinguish it 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 Guidelines5/5

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

It gives an explicit alternative rule ('For simple back-to-back concatenation use var2_join_videos instead') and routes post-render polling to var2_check_join_status. The render=false vs render=true split is framed as save-now versus queue-render, so the agent knows which mode to pick.

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