OpenClip

Render Clip Tool

render_clip

Produce a final captioned render of one viral moment. Pass the video id and the moment's viral_moment id (both hashids from list_clips), and an optional caption_preset (a supported preset key; invalid keys are rejected).

This is an EXPLICIT, on-demand render: calling it (re)renders the moment now. If a rendered clip already exists it is REPLACED — e.g. call again with a different caption_preset to re-render in a new style. To just read an existing render, use get_render_status or list_clips instead.

Rendering is ASYNCHRONOUS: this returns status: "rendering" once dispatched — then poll get_render_status with the same ids until it reports completed and a rendered_clip URL. Safe to retry: a render already in flight returns rendering without starting a second one. not_dispatched means a precondition wasn't met (no preview clip, or the renderer isn't configured).

Input Schema

TableJSON Schema

Name	Required	Description
`video`	Yes	The video id (hashid) from list_videos / list_clips.
`viral_moment`	Yes	The viral moment id (hashid) from list_clips.
`caption_preset`	No	Optional caption preset key applied to the render (invalid keys are rejected).

Output Schema

TableJSON Schema

Name	Required	Description
`video`	Yes	The video id (hashid) the render belongs to.
`status`	Yes	`rendering` means a render is in flight (poll get_render_status); `not_dispatched` means a precondition was not met, so nothing is in flight.
`viral_moment`	Yes	The rendered viral moment id (hashid). Poll get_render_status with these two ids.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "status": {
+      "description": "`rendering` means a render is in flight (poll get_render_status); `not_dispatched` means a precondition was not met, so nothing is in flight.",
+      "enum": [
+        "rendering",
+        "not_dispatched"
+      ],
+      "type": "string"
+    },
+    "video": {
+      "description": "The video id (hashid) the render belongs to.",
+      "type": "string"
+    },
+    "viral_moment": {
+      "description": "The rendered viral moment id (hashid). Poll get_render_status with these two ids.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "video",
+    "viral_moment",
+    "status"
+  ],
+  "type": "object"
+}

First observedJul 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly reveals that rendering is asynchronous, that existing renders are replaced, that in-flight renders are idempotent, and what not_dispatched indicates.

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 and front-loaded: purpose, explicit behavior, async instructions, retry semantics, and failure meaning. Every sentence adds necessary information with no 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 an asynchronous tool with two required string ids and one optional preset, it covers dispatch, polling, replacement, retries, and preconditions. Return-value details are appropriately deferred to the output schema.

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 coverage is 100%, so the baseline is 3. The description reinforces that both ids are hashids from list_clips and that caption_preset supports preset keys, but it does not add substantial meaning beyond the schema's already explicit parameter descriptions.

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 opens with a specific verb and resource: 'Produce a final captioned render of one viral moment.' It clearly distinguishes this action tool from read-only siblings like get_render_status and list_clips by framing it as an explicit, on-demand render.

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?

It gives explicit when-to-use and when-not-to-use guidance: call this to (re)render now, and use get_render_status or list_clips to just read an existing render. It also covers safe retry behavior and the meaning of not_dispatched.

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

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

Resources

Need Help?