Skip to main content
Glama
Sign In

cliphou.se release videos

by se.cliphou
OverviewDiscussionsAdmin

Render personalized preview

render_preview
Idempotent

Render a poster image of a template filled with the user's props, in a few seconds, and return it with the editor link. Call after get_template_spec once the props are filled, and show the image to the user. Invalid props return an error that names the field to fix. If rendering is unavailable, poster is null and the editor link still works. With loop: true it also waits for a 4-second animated WebP loop of these props and returns it as video. A loop still rendering has video: null and videoPending: true; call again with the same props to get it. loop: "start" returns the poster now and starts the loop in the background. Show the loop as an image (Markdown title) where the host renders images.

Input Schema

NameRequiredDescriptionDefault
loopNotrue waits for a 4-second animated loop of these props and returns it as video. "start" only starts it.
propsYesThe full props object from get_template_spec with edited texts, theme, and media.
searchIdNoThe searchId returned by search_templates. Pass it through so picks can be measured.
variantIdYesTemplate id.
templateVersionNoOnly for older template versions. Usually omit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / loop
      Added value: +{
+  "anyOf": [
+    {
+      "const": "start",
+      "type": "string"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "true waits for a 4-second animated loop of these props and returns it as video. \"start\" only starts it."
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare safety/idempotency; the description adds latency ('a few seconds'), error semantics ('invalid props return an error that names the field to fix'), graceful degradation ('poster is null and the editor link still works'), and the async polling contract (video: null + videoPending: true, call again with same props). This is unusually rich behavioral disclosure beyond the structured fields.

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?

Leading sentence front-loads the purpose, and each subsequent sentence carries a distinct actionable fact (error handling, unavailability fallback, loop modes, polling, display format). Dense but zero 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?

With no output schema present, the description fully compensates by describing return fields (poster, editor link, video, videoPending) and their null-state meanings. An agent has everything needed to call it correctly and interpret the response.

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 coverage is 100%, so baseline is 3, but the description adds workflow meaning the schema lacks — the retry-until-not-pending pattern for loop and the distinction that 'start' returns the poster immediately while true blocks. That elevates it above baseline without fully re-documenting every 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 (render), resource (poster image of a template filled with the user's props), and deliverables (image plus editor link). An agent can immediately tell this apart from get_template_spec and build_edit_link, which only supply the spec and link respectively.

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?

Explicit sequencing: 'Call after get_template_spec once the props are filled, and show the image to the user,' with clear conditions for the loop modes. It doesn't name the sibling render_previews (plural) as an alternative or state a when-not-to-use condition, so it falls just short of 5.

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

All cliphou.se release videos 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