Skip to main content
Glama

rerender

Regenerates a video using settings from a previous render; omit seed to retry identical output, use -1 for variation or a number to control randomness.

Instructions

Makes a video again with the settings of an earlier one (a name from list_videos). seed: leave out for the same seed (same video, e.g. after a crash), -1 for a new variation, or a number.

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": {
      "video": "<video>"
    },
    "name": "rerender"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNo
videoYes
promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare non-readOnly, non-destructive, closed-world, so the safety profile is covered. The description adds genuine behavior detail — determinism of the seed and the crash-recovery use case — but leaves a key ambiguity for a mutation tool: whether the re-render replaces the original video or produces a separate one, and what happens to the original.

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?

Two sentences, front-loaded with the core action before the seed detail, with no filler. The seed sentence is written as a compressed colon-fragment list, which is dense but still readable.

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

Completeness2/5

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

For a mutation tool with no output schema and 0% schema coverage, the description omits the undocumented 'prompt' parameter entirely and says nothing about the result of the call — whether a new video entry is created, whether the original is overwritten, or what identifier is returned to track the job.

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 0%, so the description must carry the burden. It explains 'video' (a name from list_videos) and gives thorough semantics for 'seed' that go well beyond the schema's bare integer type, but the third parameter 'prompt' is never mentioned, leaving it undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: re-generates a video using the settings of an earlier one, and points to list_videos as the source of the video identifier. It does not distinguish itself from the sibling build_video, which likely creates a video from scratch, so an agent still has to infer which of the two to pick for a fresh render.

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

Usage Guidelines3/5

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

Usage guidance is strong at the parameter level (leave out seed to reproduce the same video, e.g. after a crash; -1 for a variation), but there is no tool-level guidance about when to choose rerender over build_video or other video-creation siblings.

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