Clipform

Check Render Status

clipform_check_render

Read-onlyIdempotent

Check the status of render jobs started by clipform_render_video_template or clipform_render_composition.

Pass job_ids to check a whole batch in ONE call - one line of status per job. Pass job_id for a single job. Returns the output URL for each completed render. Typical render time: 10-60 seconds. Attach is automatic when node_id was provided to the render tool - no need to poll to completion, and the attach outcome is reported here once known.

Input Schema

TableJSON Schema

Name	Required	Description
`job_id`	No	A single job ID returned by the render tool
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.
`job_ids`	No	Multiple job IDs - check the whole batch in one call instead of one call per job

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobs`	Yes	One entry per queried job; attach completed public_urls via upload_media_asset then attach_node_media unless already auto-attached

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

addedInput schema / properties / job_id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

addedInput schema / properties / job_ids / items / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

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

Changed5 schema fields changedJul 17, 2026

changedOutput schema / properties / jobs / description

Previous value: -"One entry per queried job; attach completed public_urls via upload_media_asset then attach_node_media"New value: +"One entry per queried job; attach completed public_urls via upload_media_asset then attach_node_media unless already auto-attached"

addedOutput schema / properties / jobs / items / properties / attach_error

Added value: +{
+  "description": "Present when node_id was set but auto-attach failed - the render itself still succeeded.",
+  "type": "string"
+}

addedOutput schema / properties / jobs / items / properties / attached

Added value: +{
+  "description": "True when the render's node_id was set and it attached to the node automatically.",
+  "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"
+}

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 / description

Previous value: -"One entry per queried job; attach completed public_urls via upload_node_media"New value: +"One entry per queried job; attach completed public_urls via upload_media_asset then attach_node_media"

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 queried job; attach completed public_urls via upload_node_media",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "duration_seconds": {
+            "type": "number"
+          },
+          "elapsed_seconds": {
+            "type": "number"
+          },
+          "error": {
+            "type": "string"
+          },
+          "job_id": {
+            "type": "string"
+          },
+          "public_url": {
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "rendering",
+              "complete",
+              "failed",
+              "not_found"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "job_id",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "jobs"
+  ],
+  "type": "object"
+}

First observedJul 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: typical render time of 10-60 seconds, and the non-obvious fact that attachment happens automatically when node_id was supplied and its outcome surfaces here. It stops short of, say, failure/error semantics for jobs that never complete.

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?

Four sentences, all load-bearing, ordered from what the tool does to how to call it to what comes back. The batching instruction and the attach-automation note are front-loaded where an agent will see them. Minimal overlap with the output schema beyond one short clause.

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?

With an output schema present, return values need not be re-explained, and the description wisely limits itself to one line about output URLs. Between the annotations, the output schema and this description, an agent has everything needed to call it correctly, including the timing expectation that prevents premature polling.

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?

Schema description coverage is 100%, so the baseline is 3. The description earns above baseline by explaining the semantic distinction the schema cannot: job_ids is a batching mechanism ('one line of status per job') rather than a plain array, and job_id vs job_ids are alternatives rather than combinable filters.

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+resource ('Check the status of render jobs') and scopes it to jobs created by clipform_render_video_template or clipform_render_composition. This distinguishes it cleanly from siblings like clipform_get_results or clipform_get_node_media without needing to open any 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?

Explicitly routes the agent: use job_ids to check a batch in one call, job_id for a single job. It also resolves the implicit question of whether to poll, stating 'no need to poll to completion' because attach is automatic. Both the when and the when-not are covered.

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.