Skip to main content
Glama
osbytes

reelsaw

by osbytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Re-render clips

rerender_clips
Idempotent

Queue multiple clips from one project to render again after edits or failures; clips still rendering are skipped, and completed videos replace the old ones.

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 }; poll get_project or wait_for_project. For a single clip rerender_clip is enough.

Input Schema

TableJSON 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?

Goes well beyond the lone idempotentHint annotation: it states which clips are queued versus skipped (finished/failed queued, still-rendering skipped), that each new video replaces the old on completion, and names the return payload. This is exactly the behavioral context an agent needs for a mutation-queue tool.

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?

Four tight sentences: purpose, queue/skip semantics, return shape plus polling hint, and the sibling redirect, in that order. No filler and nothing redundant with the schema.

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 a two-param batch mutation with no output schema, the description covers the trigger, the skip/replace semantics, the exact return shape, and the follow-up polling tools. Nothing an agent needs to call it correctly is missing.

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%, with clipIds documenting the 1-200 bound and projectId its source, so the schema already carries the parameter semantics. The description adds no syntax or format detail beyond referring to 'several clips of one project', 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 and resource ('Queue several clips of one project for rendering again') with scope ('in one step') and contrasts it against the single-clip sibling rerender_clip. An agent can distinguish it from rerender_clip and retry_project without opening any schema.

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 the trigger conditions ('after edits or failures') and explicitly names the alternative for a narrower use case ('For a single clip rerender_clip is enough'). When-to-use and when-to-use-something-else are both present.

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