Clipform

Render Video Template

clipform_render_video_template

Destructive

Render a curated video template (a pre-arranged Scene: bed + overlay + sane defaults) to MP4 or PNG from a small controls object, instead of hand-assembling Scene layers. Call clipform_list_video_templates first for available template names and their controls. Renders through the Scene composition under the hood.

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`wait`	No	true (default) blocks until the render is ready and returns its URL; false returns a job ID for clipform_check_render.
`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).
`node_id`	No	Form node to attach this render to automatically once it completes - skips the manual clipform_upload_media_asset + clipform_attach_node_media steps and republishes the form if it's currently live. Requires form_id.
`captions`	No	Word-level captions from clipform_generate_tts - carried onto the attached media asset. Only used when node_id is set.
`controls`	Yes	Template-specific controls (see clipform_list_video_templates for the exposed control surface).
`template`	Yes	Video template name (see clipform_list_video_templates).
`caption_ref`	No	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.
`outputFormat`	No	Output format (default: mp4)	mp4

Output Schema

TableJSON Schema

Name	Required	Description
`job_id`	No	Present when status is 'rendering' - pass to clipform_check_render
`status`	Yes
`attached`	No	True when node_id was provided and the render was attached to the node automatically (present once the attach outcome is known).
`template`	No
`public_url`	No	Present when status is 'complete' - attach via upload_media_asset then attach_node_media (fit_media: true), unless node_id was set (auto-attached)
`republished`	No	True when the form was live and was republished to include this media.
`attach_error`	No	Present when node_id was provided but auto-attach failed - the render itself still succeeded.
`output_format`	No
`media_asset_id`	No	The workspace media asset created from this render, when attached.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

addedInput schema / 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"
+}

Changed3 schema fields changedSep 5, 2026

changedInput schema / 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 / captions / items / properties / words / minItems
```
Added value: +1
```

changedInput schema / 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"
+}

changedInput schema / required

Previous value: -[
-  "template",
-  "controls"
-]New value: +[
+  "template",
+  "controls",
+  "context"
+]

Changed8 schema fields changedJul 17, 2026

addedInput schema / 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 / form_id

Added value: +{
+  "description": "The form UUID (required when node_id is set).",
+  "format": "uuid",
+  "type": "string"
+}

addedInput schema / properties / node_id

Added value: +{
+  "description": "Form node to attach this render to automatically once it completes - skips the manual clipform_upload_media_asset + clipform_attach_node_media steps and republishes the form if it's currently live. Requires form_id.",
+  "type": "string"
+}

addedOutput schema / 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 / 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 / media_asset_id

Added value: +{
+  "description": "The workspace media asset created from this render, when attached.",
+  "type": "string"
+}

changedOutput schema / 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 / republished

Added value: +{
+  "description": "True when the form was live and was republished to include this media.",
+  "type": "boolean"
+}

AddedJul 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Discloses key runtime behavior beyond annotations: rendering happens through Scene composition, results are not finalized until attached to a node, passing node_id auto-attaches and republishes live forms, and the caller should fire-and-forget rather than poll. This matches the destructiveHint/idempotentHint annotations and adds useful operational detail.

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 well-structured: core purpose, tool-selection guidance, and attachment workflow each occupy their own paragraph. A few phrases like 'under the hood' add slight redundancy, but every section serves a clear informational purpose.

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?

Given the tool's complexity and large sibling set, the description supplies prerequisites, alternative tool guidance, async behavior, attachment/republish side effects, and pointers to related tools (list_video_templates, check_render). It does not deeply explain error states or output schema details, but those are partially covered by the schema and sibling references.

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 covers all 9 parameters with 100% description coverage, so the narrative parameter guidance is a bonus rather than a necessity. The description reinforces the source of 'controls' and the relationship between node_id/form_id, but does not substantially exceed the schema's per-parameter explanations.

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?

Clearly states the action (render), the resource (curated video template), the output formats (MP4/PNG), and distinguishes it from hand-assembling Scene layers and other sibling render tools. No ambiguity about what the tool does.

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?

Explicitly instructs the caller to call clipform_list_video_templates first, provides a decision tree for choosing this tool versus clipform_generate_video or clipform_render_composition, and warns against polling or manually chaining upload/attach steps when node_id is provided.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.