Clipform

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.

For narrated Ken Burns slideshows from images, use clipform_generate_video instead. 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

Name	Required	Description	Default
`wait`	No	Single 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.
`items`	No	Batch 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.
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.
`form_id`	No	The form UUID - required when node_id is set (single render) or any item sets node_id (batch).
`node_id`	No	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.
`captions`	No	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.
`inputProps`	No	Single 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`.
`outputFormat`	No	Single render: output format (default: mp4)	mp4
`compositionId`	No	Single 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

Name	Required	Description	Default
`jobs`	Yes	One entry per render (single or batch)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedSep 5, 2026
- 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"
+]
```

Changed3 schema fields changedAug 31, 2026

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"
+]
```

Changed10 schema fields changedJul 17, 2026

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"
+}

Changed1 schema field changedJul 13, 2026

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)"

Changed1 schema field changedJul 10, 2026

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."

Changed1 schema field changedJul 8, 2026

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"
+}

Changed1 schema field changedJul 7, 2026

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."

First observedJul 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description richly discloses behavior beyond the annotations: wait:true blocks and returns a URL, wait:false returns a job ID, batch renders fire in parallel, inputProps are strictly validated, map-wide shots may round coordinates, and completed renders auto-attach to form nodes. This goes well beyond the destructiveHint/readOnlyHint annotations and gives the agent accurate expectations.

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 long but organized into clearly front-loaded paragraphs covering purpose, alternatives, modes, routing, and attachment behavior. It earns most of its length given the tool's complexity, but there is some redundancy, for example the clipform_generate_video guidance appears both early and again in the 'Choosing a render tool' section.

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 tool with 9 parameters, nested objects, an output schema, and many siblings, the description is remarkably complete. It covers output formats, single vs batch behavior, result retrieval, alternatives, attachment semantics, and common pitfalls, so an agent has enough context to invoke the tool correctly without additional research.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description reinforces parameter-related usage choices (items, wait, node_id, form_id), but most of that meaning is already present in the input schema descriptions. It adds workflow context but not much genuinely new parameter semantics beyond the structured fields.

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 and resource: 'Render a specialised video composition to MP4 or PNG'. It also distinguishes itself from clipform_generate_video by stating it covers 'custom animated visuals' such as geography animations or designed motion graphics, making the tool's purpose unmistakable relative to siblings.

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' section explicitly tells the agent when to prefer clipform_render_video_template, when to use clipform_generate_video, and when to fall back to this tool. It also gives clear batch-vs-single guidance and explains the correct node-attachment workflow, including what not to do (do not poll clipform_check_render or manually chain upload/attach).

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

All Clipform tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have clearly distinct purposes: form CRUD, node management, media upload/attach, rendering, search, and guidance retrieval are all separable. The main overlap is among the three render tools (clipform_generate_video, clipform_render_video_template, clipform_render_composition), but their descriptions include explicit disambiguation guidance, so an agent can correctly choose. clipform_get_guide and clipform_get_workflow are also similar but clearly differentiated.

Naming Consistency4/5

Tool names follow a consistent clipform_<verb>_<noun> pattern throughout, e.g., clipform_create_form, clipform_add_node, clipform_update_node, clipform_delete_node. Minor deviations exist: clipform_whoami is not verb_noun, and get_more_tools lacks the clipform_ prefix, but these are edge cases and the overall convention is highly predictable.

Tool Count3/5

34 tools is on the heavy side for a single MCP server. The server covers a broad domain (form creation, node editing, media management, video rendering, TTS, search, guidance, imports, responses), so the count is defensible, but it is above the typical well-scoped range and may add navigation overhead.

Completeness5/5

The tool surface covers the full lifecycle: create/read/update/delete forms and nodes, media upload/attach/delete, multiple render paths with status checking, TTS generation, music/image/video search, form import, response retrieval, and workflow/guide knowledge. The main gap is lack of a direct branching-logic editor (option-based branching is only in the dashboard), but the API consciously documents that limitation and the rest of the lifecycle is complete.

Render Composition

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources