Clipform

List Video Templates

clipform_list_video_templates

Read-onlyIdempotent

Browse available video templates - curated Scene arrangements (bed + overlay + sane defaults) that render through the Scene composition from a small controls object. Call this before clipform_render_video_template to see template names and their exposed controls. For a fully custom layer stack, assemble Scene layers directly via clipform_render_composition instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`templates`	Yes	Available video templates - pass a name + controls to clipform_render_video_template

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 31, 2026

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

Changed1 schema field changedJul 17, 2026

addedOutput schema / properties / templates / items / properties / exampleControls

Added value: +{
+  "additionalProperties": {},
+  "description": "A worked, ready-to-render controls object for this template - copy and adapt it",
+  "type": "object"
+}

AddedJul 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond annotations by explaining what templates are (bed + overlay + sane defaults) and scoping the result contents ('template names and their exposed controls'). No contradiction exists between the description and annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: the first defines the concept, the second gives usage sequencing, and the third routes to an alternative. The action is front-loaded and there is zero filler.

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 simple read-only list tool with a fully documented single parameter, a rich output schema, and complete safety annotations, the description closes all remaining gaps: domain vocabulary, expected output contents, and call sequencing. Nothing an agent needs to select and invoke it correctly is missing.

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%; the single required context parameter is already well-documented ('Describe the user's underlying goal in one sentence - not the tool you're calling'). The description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 uses a specific verb ('Browse') with a clear resource ('available video templates') and grounds it conceptually ('curated Scene arrangements (bed + overlay + sane defaults)'). It also explicitly differentiates itself from clipform_render_video_template and clipform_render_composition, so an agent can tell the tools apart without opening schemas.

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 sequencing guidance ('Call this before clipform_render_video_template to see template names and their exposed controls') and an explicit alternative ('For a fully custom layer stack, assemble Scene layers directly via clipform_render_composition instead'). This is exactly the when/when-not/alternatives guidance the dimension requires.

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.