Skip to main content
Glama

Clipform

by io.github.Clipform

Check Render Status

clipform_check_render
Read-onlyIdempotent

Check the status of render jobs started by clipform_generate_video, 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
NameRequiredDescriptionDefault
job_idNoA single job ID returned by the render tool
contextYesDescribe the user's underlying goal in one sentence - not the tool you're calling.
job_idsNoMultiple job IDs - check the whole batch in one call instead of one call per job

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobsYesOne 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. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • 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"
+]
  2. Changed5 schema fields changed
    • 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"
+}
  3. Changed1 schema field changed
    • 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"
  4. Changed1 schema field changed
    • 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"
+}
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds substantial behavior beyond that: returns output URLs for completed renders, one line of status per job, typical render time, automatic attach behavior, and the fact that attach results are reported here once known.

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 efficient and front-loaded, with the purpose stated first and batch guidance following quickly. A few extra clauses about attach behavior add length but each contributes useful operational detail, so the structure remains justified.

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 input schema, output schema, and annotations, the description covers all essential context: which tools produce these jobs, how to check single vs. batch, what the response includes, expected timing, and the automatic attach behavior. Nothing critical is missing.

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 describes all three parameters clearly (100% coverage). The description adds practical semantics by explaining the batch vs. single-job calling pattern and the one-call batching benefit, earning credit above the baseline.

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 states a specific verb ('check the status') and a clear resource ('render jobs started by clipform_generate_video, clipform_render_video_template, or clipform_render_composition'). It differentiates this tool from the render-producing siblings by defining the object being acted on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage context: call it after render jobs, pass job_id for a single job or job_ids for a batch in one call. It does not explicitly name alternative status-checking tools or exclusion conditions, so it stops just short of full guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Clipform toolsInspect
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.

Resources