Clipform

List Compositions

clipform_list_compositions

Read-onlyIdempotent

Browse available video compositions and their expected props schemas. Call this before using clipform_render_composition to discover visual styles and their input props. For an image or photo montage, reach for a video template (clipform_list_video_templates + clipform_render_video_template) or clipform_generate_video instead of a composition.

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
`compositions`	Yes	Available compositions - pass an id to render_composition

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 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "compositions": {
+      "description": "Available compositions - pass an id to render_composition",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "durationInFrames": {
+            "type": "number"
+          },
+          "fps": {
+            "type": "number"
+          },
+          "height": {
+            "type": "number"
+          },
+          "id": {
+            "type": "string"
+          },
+          "props": {
+            "description": "Compact props summary (name*: type)",
+            "type": "string"
+          },
+          "propsSchema": {
+            "additionalProperties": {},
+            "description": "Full JSON Schema for inputProps",
+            "type": "object"
+          },
+          "width": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "width",
+          "height",
+          "fps",
+          "durationInFrames",
+          "props"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "compositions"
+  ],
+  "type": "object"
+}

First observedJul 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds useful context beyond that: the call is a discovery/listing operation whose payoff is the props schema, and it is a prerequisite step to rendering. It stops short of stating pagination or result size, keeping it at a 4.

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 the core purpose, then prerequisite ordering, then exclusions – a sensible information hierarchy. The final sentence is dense (three sibling tool names in one clause) but each name earns its place as a routing target.

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?

An output schema exists, so return values need not be explained; the description instead covers the remaining agent needs – when to call it, what it enables downstream, and which tools to prefer for montage use cases. Nothing needed to 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% and the single 'context' parameter is fully documented in the schema, so the baseline is 3. The description adds no extra guidance on how to phrase the context string, which is the only parameter.

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 ('Browse available video compositions') and goes further by naming the expected output ('their expected props schemas'). It explicitly distinguishes itself from clipform_render_composition and the video-template siblings, so an agent can place it without opening a 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?

Gives explicit ordering guidance ('Call this before using clipform_render_composition') and a concrete when-not/alternative branch ('For an image or photo montage, reach for clipform_list_video_templates + clipform_render_video_template or clipform_generate_video'). Both the correct path and the wrong path are named.

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.