Skip to main content
Glama

render_scene

Render scene specs into MP4/MOV b-roll videos with customizable tracks for titles, lists, flows, comparisons, and hubs. Create branded overlays for short-form video without After Effects.

Instructions

Render a scene spec to an MP4 (or .mov if background is 'transparent'). Returns { ok, outPath, durationSeconds, codec }. Defaults to 9:16 portrait (1080x1920) at 30fps; set width=1920, height=1080 for landscape. Duration must be 4-6 seconds. PICK THE TRACK KIND BY CONTENT SHAPE, not by default. Do not reach for 'list-reveal' unless the content is genuinely a flat enumeration of >=3 peer items. Use 'flow' when describing a pipeline / sequence / before→after path (A → B → C). Use 'hub' when one central concept connects to 2-4 related satellites. Use 'comparison' for a two-sided contrast (old vs new, before vs after). Use 'title-overlay' for a hero text card with no diagram. Call list_examples first to see a canonical spec for each kind before authoring. Both portrait (1080x1920, default — reels / shorts / TikTok) and landscape (1920x1080 — YouTube / LinkedIn / web embeds) are supported; ask the user or infer from context which they want. Layouts auto-flip (e.g. 'flow' is vertical in portrait, horizontal in landscape).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specYesA scene spec. Top-level: { id, durationFrames, fps?, width?, height?, theme?, background?, backgroundImage?, palette?, tracks[] }. durationFrames/fps MUST be between 4 and 6 seconds. Default fps=30, width=1080, height=1920. theme='light' (default) or 'dark' selects the Wednesday Solutions palette. background overrides the theme's canvas color; set 'transparent' for an alpha-channel .mov render. backgroundImage={source(URL or public/ path), opacity?=1, fit?='cover'|'contain', tint?, tintOpacity?=0} renders behind tracks. palette={background?, ink?, inkMuted?, inkDim?, accent?, accentDeep?, hairline?} overrides individual theme colors. Each track has { kind, id, startFrame, endFrame, enter?, exit? } plus kind-specific fields. Kinds: 'title-overlay' (text), 'list-reveal' (rows[].{text, iconName?, revealAtFrame}, position{x,y}), 'flow' (nodes[].{iconName, label}, position{x,y}, direction='horizontal', revealCadenceFrames=35 — left-to-right icon flow with arrows drawing between them), 'comparison' (left{iconName,label,subLabel?}, right{iconName,label,subLabel?}, divider{label='vs', showLine=true} — side-by-side contrast with a center divider), 'hub' (center{iconName,label}, satellites[2-4].{iconName,label}, position{x,y}, revealCadenceFrames=22 — central icon with N satellites connecting in via lines), 'icon' (name, position, sizePx?, color?), 'text' (text, position, fontSizePx?, color?), 'lottie' (source, position, sizePx?, loop?). Position x,y are 0..1 fractions of canvas.
outPathNoAbsolute or repo-relative path to write the rendered file. If omitted, writes to <kit>/output/<spec.id>.<mp4|mov>.
Behavior5/5

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

With no annotations, the description carries full responsibility. It discloses return values, default resolution, fps, duration constraints, transparent background behavior, and auto-flipping layout, giving a thorough view of the tool's behavior.

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 description is front-loaded with the core purpose and returns, followed by essential guidance on track kinds and orientation. It is lengthy but each sentence serves a purpose; however, it could be condensed and organized for even quicker consumption.

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?

Given the complexity of the spec object and no output schema, the description covers return format, constraints, orientation choices, and references list_examples for canonical specs. It is complete for an agent to use the tool effectively.

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?

The input schema already has 100% description coverage, so baseline is 3. The description adds value by explaining track-kind selection rules and orientation flipping, which are semantic nuances beyond the schema's field definitions.

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 clearly states the tool renders a scene spec to an MP4 (or .mov) and returns a structured result. It distinguishes itself from siblings like list_examples and validate_scene by focusing on the actual rendering output.

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?

Provides explicit, detailed guidance on when to use each track kind based on content shape, and directs agents to call list_examples first. It also covers orientation selection and how to ask the user or infer from context, making usage conditions very clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alichherawalla/video-overlay-kit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server