Skip to main content
Glama

Render a clip

clipember_render_clip

Render the clip with its current edits (the draft from clipember_edit_clip or the editor, else the saved version). Free — re-rendering your own clip doesn't use a video from your plan. Check progress with clipember_get_clip.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clipId": "<clipId>"
    },
    "name": "clipember_render_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses three things an agent could not infer: which content source is used (draft precedence over saved), that the operation is asynchronous and must be polled via clipember_get_clip, and that it consumes no plan video credit. These are the behaviors that actually determine correct invocation, and none of them contradict the structured hints.

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?

Three short clauses, front-loaded with the action and content source, then cost, then the follow-up call. Every sentence carries information the agent would otherwise have to guess, and there is no filler.

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?

For a one-parameter async mutation with no output schema, the definition covers what is rendered, the cost model, and how to track completion. It does not say what the render call itself returns (a job handle, a status) before switching to clipember_get_clip, a minor gap given no output schema exists.

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 0% for the single parameter, so the schema supplies only a name, a uuid format, and a pattern. The description never explains clipId, though the name and its phrase "your own clip" make the meaning self-evident. Adequate by inference rather than by explicit documentation.

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?

"Render the clip with its current edits" gives a specific verb and resource, and the parenthetical resolves the key ambiguity about which content is rendered (draft vs. saved version). It names the sibling that produces the draft (clipember_edit_clip), so an agent can place it in the workflow without opening another schema.

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?

It states the triggering condition clearly: call this after edits to apply the current draft, falling back to the saved version. The credit note ("re-rendering your own clip doesn't use a video from your plan") removes a real hesitation about cost, and pointing to clipember_get_clip for progress tells the agent the next step. No explicit 'when not to use' is given, which keeps it just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources