Skip to main content
Glama

Render Composition

clipform_render_composition
Destructive

Render a specialised video composition to MP4 or PNG - custom animated visuals that clipform_generate_video can't provide, such as geography animations or designed motion graphics. Available composition names and their required input props schemas come from clipform_list_compositions.

Output formats: mp4 (H.264, best for social media) or png (single frame). Returns a public URL when complete.

For multi-render builds (e.g. one clip per quiz question), pass everything in ONE call via items (max 10): all renders fire in parallel and you get one job ID each - then collect the URLs in a single clipform_check_render call with job_ids. Single render: pass compositionId/inputProps at the top level (wait: true blocks and returns the URL; wait: false returns a job ID).

Choosing a render tool: for a recognisable form/quiz beat (guess-the-city, this-or-that, mystery reveal, multiple choice, photo montage...) reach for a video template first (clipform_list_video_templates + clipform_render_video_template) - it is a one-call recipe. Use clipform_generate_video for a narrated or audio-synced media montage (images/clips timed to a voice track). Use clipform_render_composition only when neither fits and you need a custom layer stack. A render for a form node is not done until it is attached to that node. Pass node_id (and form_id) so the completed render attaches itself automatically - do not poll clipform_check_render to completion or manually chain clipform_upload_media_asset + clipform_attach_node_media; fire the render and move on. In batch mode, set node_id per item (see items) and form_id once at the top level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoSingle render only: true (default) blocks until the render is ready and returns its URL; false returns a job ID for clipform_check_render. Batch items always run fire-and-poll.
itemsNoBatch mode: multiple renders in one call. All fire in parallel; returns one job ID per item - collect with clipform_check_render (job_ids). Use this whenever rendering more than one clip.
contextYesDescribe the user's underlying goal in one sentence - not the tool you're calling.
form_idNoThe form UUID - required when node_id is set (single render) or any item sets node_id (batch).
node_idNoSingle render only: form node to attach this render to automatically once it completes. Requires form_id. For batch mode, set node_id per item instead.
captionsNoSingle render only: word-level captions from clipform_generate_tts, carried onto the attached media asset. Only used when node_id is set. For batch mode, set captions per item instead.
inputPropsNoSingle render: props object matching the composition's schema from clipform_list_compositions. Validated STRICTLY - unknown or missing props fail with the schema in the error, nothing renders silently with defaults. For map compositions (Map), wide shots (camera.zoom < 9) may round lat/lng to 1 decimal place to improve cache hit rates; close shots and pin drops should keep full precision — the pin lands exactly on `target`.
caption_refNoSingle render only: caption_ref from clipform_generate_tts - an opaque handle that attaches that TTS run's word-level captions to the media asset, resolved server-side. Preferred over captions. Only used when node_id is set. For batch mode, set caption_ref per item instead.
outputFormatNoSingle render: output format (default: mp4)mp4
compositionIdNoSingle render: the composition ID. Call clipform_list_compositions to see available options (e.g. 'Slideshow', 'Map', 'Grid'). Use items instead for multiple renders.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobsYesOne entry per render (single or batch)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / caption_ref
      Added value: +{
      +  "description": "Single render only: caption_ref from clipform_generate_tts - an opaque handle that attaches that TTS run's word-level captions to the media asset, resolved server-side. Preferred over captions. Only used when node_id is set. For batch mode, set caption_ref per item instead.",
      +  "type": "string"
      +}
    • addedInput schema / properties / items / items / properties / caption_ref
      Added value: +{
      +  "description": "caption_ref from clipform_generate_tts - an opaque handle that attaches that TTS run's word-level captions to the media asset, resolved server-side. Preferred over captions. Only used when node_id is set.",
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / items / items / properties / captions / items / properties / words / description
      Previous value: -"Per-word timestamps within the segment"New value: +"Per-word timestamps within the segment. Required - copy the full array from clipform_generate_tts verbatim."
    • addedInput schema / properties / items / items / properties / captions / items / properties / words / minItems
      Added value: +1
    • changedInput schema / properties / items / items / properties / captions / items / required
      Previous value: -[
      -  "start",
      -  "end",
      -  "text"
      -]New value: +[
      +  "start",
      +  "end",
      +  "text",
      +  "words"
      +]
  3. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's underlying goal in one sentence - not the tool you're calling.",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context"
      +]
  4. Changed10 schema fields changed
    • addedInput schema / properties / captions
      Added value: +{
      +  "description": "Single render only: word-level captions from clipform_generate_tts, carried onto the attached media asset. Only used when node_id is set. For batch mode, set captions per item instead.",
      +  "items": {
      +    "$ref": "#/properties/items/items/properties/captions/items"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / form_id
      Added value: +{
      +  "description": "The form UUID - required when node_id is set (single render) or any item sets node_id (batch).",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • addedInput schema / properties / items / items / properties / captions
      Added value: +{
      +  "description": "Word-level captions from clipform_generate_tts - carried onto the attached media asset. Only used when node_id is set.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "end": {
      +        "description": "Segment end time in seconds",
      +        "type": "number"
      +      },
      +      "start": {
      +        "description": "Segment start time in seconds",
      +        "type": "number"
      +      },
      +      "text": {
      +        "description": "Full segment text",
      +        "type": "string"
      +      },
      +      "words": {
      +        "description": "Per-word timestamps within the segment",
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "end": {
      +              "type": "number"
      +            },
      +            "start": {
      +              "type": "number"
      +            },
      +            "word": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "word",
      +            "start",
      +            "end"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "start",
      +      "end",
      +      "text"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / items / items / properties / node_id
      Added value: +{
      +  "description": "Form node to attach this item's render to automatically once it completes. Requires the batch's top-level form_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / node_id
      Added value: +{
      +  "description": "Single render only: form node to attach this render to automatically once it completes. Requires form_id. For batch mode, set node_id per item instead.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / jobs / items / properties / attach_error
      Added value: +{
      +  "description": "Present when node_id was provided but auto-attach failed - the render itself still succeeded.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / jobs / items / properties / attached
      Added value: +{
      +  "description": "True when node_id was provided and the render was attached to the node automatically (present once the attach outcome is known).",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / jobs / items / properties / media_asset_id
      Added value: +{
      +  "description": "The workspace media asset created from this render, when attached.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / jobs / items / properties / public_url / description
      Previous value: -"Present when status is 'complete' - attach via upload_media_asset then attach_node_media (fit_media: true)"New value: +"Present when status is 'complete' - attach via upload_media_asset then attach_node_media (fit_media: true), unless node_id was set (auto-attached)"
    • addedOutput schema / properties / jobs / items / properties / republished
      Added value: +{
      +  "description": "True when the form was live and was republished to include this media.",
      +  "type": "boolean"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / properties / jobs / items / properties / public_url / description
      Previous value: -"Present when status is 'complete' - attach via upload_node_media (fit_media: true)"New value: +"Present when status is 'complete' - attach via upload_media_asset then attach_node_media (fit_media: true)"
  6. Changed1 schema field changed
    • changedInput schema / properties / compositionId / description
      Previous value: -"Single render: the composition ID. Call clipform_list_compositions to see available options (e.g. 'MediaSlideshow', 'Map', 'Grid', 'ObscuredReveal', 'Timeline', 'NumberLine', 'CountdownRing', 'CountrySilhouetteClip', 'FlagReveal', 'ColorCards', 'TitleCard', 'ParallaxImage', 'TextReveal', 'EmojiPuzzle', 'BeforeAfter'). Use items instead for multiple renders."New value: +"Single render: the composition ID. Call clipform_list_compositions to see available options (e.g. 'Slideshow', 'Map', 'Grid'). Use items instead for multiple renders."
  7. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "jobs": {
      +      "description": "One entry per render (single or batch)",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "composition_id": {
      +            "type": "string"
      +          },
      +          "job_id": {
      +            "description": "Present when status is 'rendering' - pass to check_render",
      +            "type": "string"
      +          },
      +          "output_format": {
      +            "type": "string"
      +          },
      +          "public_url": {
      +            "description": "Present when status is 'complete' - attach via upload_node_media (fit_media: true)",
      +            "type": "string"
      +          },
      +          "status": {
      +            "enum": [
      +              "rendering",
      +              "complete"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "status"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "jobs"
      +  ],
      +  "type": "object"
      +}
  8. Changed1 schema field changed
    • changedInput schema / properties / compositionId / description
      Previous value: -"Single render: the composition ID. Call clipform_list_compositions to see available options (e.g. 'MediaSlideshow', 'Map', 'Grid', 'GridList', 'ObscuredReveal', 'Timeline', 'NumberLine', 'CountdownRing', 'CountrySilhouetteClip', 'FlagReveal', 'ColorCards', 'TitleCard', 'ParallaxImage', 'TextReveal', 'EmojiPuzzle', 'BeforeAfter'). Use items instead for multiple renders."New value: +"Single render: the composition ID. Call clipform_list_compositions to see available options (e.g. 'MediaSlideshow', 'Map', 'Grid', 'ObscuredReveal', 'Timeline', 'NumberLine', 'CountdownRing', 'CountrySilhouetteClip', 'FlagReveal', 'ColorCards', 'TitleCard', 'ParallaxImage', 'TextReveal', 'EmojiPuzzle', 'BeforeAfter'). Use items instead for multiple renders."
  9. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Adds substantial behaviour beyond the annotations: batch renders fire in parallel and return one job ID per item, wait=true blocks and returns a URL while wait=false returns a job ID, returns a public URL, and auto-attachment via node_id means the render should not be polled. It does not explain why destructiveHint=true is set (e.g. whether an auto-attach overwrites existing node media) or disclose rate/limit behaviour, so one meaningful gap remains.

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 purpose, then output formats, then batch mechanics, then routing guidance — a logical order. It is fairly long, but nearly every sentence carries operational content (token budget, parallelism, attachment semantics) rather than filler, so the length is close to justified.

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 a 10-parameter tool with nested batch objects and an output schema, the description covers the essentials: what it produces, the two execution modes, how results are retrieved, how renders attach to form nodes, and how it differentiates from the other two render paths. Nothing an agent needs in order to call it correctly is 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 100%, but the description adds real meaning: inputProps are validated strictly with unknown/missing props failing rather than silently defaulting, wide map shots (camera.zoom < 9) may round lat/lng while pin drops keep full precision, and it clarifies the top-level vs per-item split for batch mode. This goes beyond restating the schema.

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 (render a specialised video composition to MP4/PNG) and immediately bounds the scope: 'custom animated visuals that clipform_generate_video can't provide, such as geography animations or designed motion graphics.' It explicitly names the sibling tools it supersedes, so an agent can distinguish it without opening any 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?

The 'Choosing a render tool' paragraph gives explicit routing rules: video templates first for recognisable form/quiz beats, clipform_generate_video for narrated/audio-synced montages, and this tool only when neither fits. It also states when to use batch vs single mode and the anti-pattern to avoid (polling to completion or manually chaining upload+attach).

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.