Skip to main content
Glama
Sign In
reelsaw

reelsaw

by osbytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Re-render clips

rerender_clips
Idempotent

Re-render multiple clips from a project in one step after edits or failures. Queues finished and failed clips, skips active renders, and returns counts to poll with get_project.

Instructions

Queue several clips of one project for rendering again in one step (after edits or failures). Finished and failed clips are queued, clips still rendering are skipped; each new video replaces the old when done. Returns { requested, rerendered, skipped, renderQueued, hint }; poll get_project or wait_for_project. For a single clip rerender_clip is enough.

Input Schema

NameRequiredDescriptionDefault
clipIdsYesClip ids of that project (get_project), 1-200
projectIdYesProject id (from list_projects, search_clips or create_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / clipIds / description
      Added value: +"Clip ids of that project (get_project), 1-200"
    • addedInput schema / properties / projectId / description
      Added value: +"Project id (from list_projects, search_clips or create_project)"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare idempotentHint=true, so the description carries the real burden and delivers: it discloses exactly which clips get queued (finished and failed), which are skipped (rendering), and replacement semantics ('each new video replaces the old when done'). It also names the return keys and the polling path, which is genuinely useful behavior an agent could not infer.

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?

Front-loaded with the action and scope, then flows into queue/skip semantics, return shape, polling, and the alternative. Every sentence earns its place 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?

No output schema exists, but the description explains the return contract ({ requested, rerendered, skipped, renderQueued, hint }) and the polling follow-up, which is exactly what an agent needs for an async batch operation.

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% with both params documented, including source tools for projectId and id/range for clipIds. The description adds no further parameter detail beyond what the schema already provides, so the baseline 3 applies.

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 (queue for re-rendering), resource (several clips of one project), and scope (one step, after edits or failures). An agent can immediately distinguish it from rerender_clip, which is explicitly named.

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?

Gives explicit when-to-use conditions (after edits or failures), when-not behavior (still-rendering clips are skipped), and names the alternative 'rerender_clip' for the single-clip case. Nothing is left to inference.

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

Deploy Server

Other Tools