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).
`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. Dates show when Glama detected each change.

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.6/5.0

Behavior5/5

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

The description goes beyond annotations by disclosing the render lifecycle: 'A render for a form node is not done until it is attached to that node,' and that passing node_id 'attaches itself automatically... and republishes the form if it's currently live.' This adds meaningful context about side effects, non-idempotence, and async behavior beyond the destructiveHint=true annotation. No contradiction with annotations.

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 longer than average but stays focused and front-loaded: the first sentence states the core action, followed by prerequisite, sibling-tool selection, and lifecycle warning. Every section earns its place, though the render-tool selection paragraph is dense and could be slightly tighter.

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 tool's complexity—8 parameters, nested captions object, output schema, and multiple sibling render tools—the description is complete. It covers prerequisites, alternative tool routing, automatic attachment behavior, republish side effects, and explicitly warns against polling or manual chaining. The output schema covers return values, so no additional return documentation is needed.

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 every parameter well. The description reinforces workflow context—such as controls being 'template-specific' and node_id enabling auto-attachment—but most of that detail is already present in the input schema. It does not add substantial new meaning for individual parameters beyond what the schema provides.

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 curated video template... to MP4 or PNG from a small controls object.' It also clarifies what the tool is not ('instead of hand-assembling Scene layers') and distinguishes it from related render tools. This makes the tool's purpose unambiguous.

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 description explicitly says when to use this tool versus siblings: use it first for recognisable form/quiz beats, use clipform_generate_video for narrated/audio-synced montages, and use clipform_render_composition only for custom layer stacks. It also gives clear workflow guidance: call clipform_list_video_templates first, pass node_id/form_id for auto-attachment, and do not poll or manually chain upload/attach steps.

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 Video Template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources