Skip to main content
Glama

OpenClip

by app.openclip
OverviewDiscussionsAdmin

Get Render Status Tool

get_render_status
Read-only

Get the render state of a video's viral moments. Pass the video id (a hashid from list_videos); optionally pass a single viral_moment id to narrow to one moment.

Each entry reports status:

  • completed — a final render exists; rendered_clip is its URL.

  • rendering — a render was dispatched and is in progress (keep polling).

  • failed — the render failed and can be requested again.

  • skipped — rendering was skipped for this moment.

  • not_rendered— no render has been requested for this moment yet.

Render completion is derived from the moment's rendered clip, not any intermediate flag. This is poll-only: re-call until completed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoYesThe video id (hashid) from list_videos.
viral_momentNoOptional: a single viral moment id to narrow the result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoYesThe video id (hashid) these renders belong to.
rendersYesOne entry per plan-visible, auto-processed viral moment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "renders": {
+      "description": "One entry per plan-visible, auto-processed viral moment.",
+      "items": {
+        "properties": {
+          "rendered_clip": {
+            "description": "URL of the final rendered clip. Null unless `status` is `completed`.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "`rendering` means keep polling; `completed` means `rendered_clip` holds the final URL; `failed`, `skipped` and `not_rendered` can all be retried with render_clip.",
+            "enum": [
+              "completed",
+              "rendering",
+              "failed",
+              "skipped",
+              "not_rendered"
+            ],
+            "type": "string"
+          },
+          "viral_moment": {
+            "description": "The viral moment id (hashid). Pass it to render_clip to (re)render this moment.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "viral_moment",
+          "status",
+          "rendered_clip"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "video": {
+      "description": "The video id (hashid) these renders belong to.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "video",
+    "renders"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral semantics: it is poll-only, 'completed' means a final render with a URL, 'failed' renders can be requested again, and completion is derived from the rendered clip rather than any intermediate flag. This is valuable behavior an agent cannot infer from the annotation alone.

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?

The description is well-structured: it front-loads the purpose and required parameter, then uses a compact bullet list for status semantics. Every sentence adds useful information, and there is no filler or duplication of the schema beyond what is helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the input IDs, optional narrowing, all status values, and the polling contract. An output schema exists, so return-value details need not be repeated. It does not explicitly mention how to trigger a render (e.g., via render_clip) when a status is 'failed' or 'not_rendered', but that is outside the tool's core responsibility and is inferable from the sibling list.

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 fully documents both parameters. The description repeats the hashid-from-list_videos hint and the optional narrowing behavior, but adds no new format, source, or validation details. Baseline 3 is appropriate given the high schema coverage.

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 the specific resource ('the render state of a video's viral moments') and the action ('get'). It clearly distinguishes itself from sibling tools like get_video_status by focusing on render state and enumerating the exact statuses. The optional viral_moment narrowing further pins down the tool's scope.

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 explicit polling guidance: 'This is poll-only: re-call until completed' and includes 'keep polling' under the rendering status. It does not explicitly name alternative tools or state when not to use this tool, but the polling context is clear enough for an agent to know when to invoke it.

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

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

Resources