Skip to main content
Glama
osbytes

reelsaw

by osbytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set clips' intro/outro

set_clip_bumpers

Override intro and outro bumpers for up to 200 clips in a project, set each to inherit, none, or a library asset, and optionally re-render only those clips.

Instructions

Override the intro and/or outro of up to 200 clips of one project: "inherit" (follow the project), "none", or a library asset id; a slot left out is untouched. rerender: true re-renders only these clips. Returns { updated, rerendered }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
introNo"inherit" (alias "default") = follow the project, "none" = no bumper on this clip, or a library asset id
outroNo"inherit" (alias "default") = follow the project, "none" = no bumper on this clip, or a library asset id
clipIdsYesClip ids of that project (get_project), 1-200 per call
introSecNoSeconds an intro image shows on these clips (1-10)
outroSecNoSeconds an outro image shows on these clips (1-10)
rerenderYestrue = re-render only these clips now; false = apply on their next render
projectIdYesProject the clips belong to (list_projects)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.0
    • addedInput schema / properties / clipIds / description
      Added value: +"Clip ids of that project (get_project), 1-200 per call"
    • addedInput schema / properties / introSec / description
      Added value: +"Seconds an intro image shows on these clips (1-10)"
    • addedInput schema / properties / outroSec / description
      Added value: +"Seconds an outro image shows on these clips (1-10)"
    • addedInput schema / properties / projectId / description
      Added value: +"Project the clips belong to (list_projects)"
    • changedInput schema / properties / rerender / description
      Previous value: -"true = re-render only these clips now"New value: +"true = re-render only these clips now; false = apply on their next render"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the partial-update semantics (omitted slots untouched), the meaning of each value mode, the rerender side effect ('re-renders only these clips'), and the return shape ({ updated, rerendered }) despite having no output schema. It omits permission requirements and what happens to clips that keep an inherited bumper.

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?

Two dense, front-loaded sentences with no filler: value modes and scope come first, then the rerender caveat, then the return shape. Every clause carries information an agent needs.

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 7-parameter mutation with no annotations and no output schema, the description covers the critical gaps: operation scope, partial-update behavior, side effects, and the return shape. It stops short of stating prerequisites (e.g. that clipIds must belong to projectId, or permission needs).

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 3 is the baseline, but the description adds value beyond it with the 200-clip cap, the slot-omission rule, and the scoping of 'rerender: true' to only the affected clips. The enum value semantics largely duplicate the schema's own parameter descriptions.

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?

The description gives a specific verb (override) and resource (intro/outro of clips) plus a hard scope bound ('up to 200 clips of one project'), which implicitly separates it from the project-level sibling set_project_bumpers. An agent can tell what this tool mutates and on which entities without opening the schema.

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 is implied by the clip-level scope and the partial-update note ('a slot left out is untouched'), but no sibling is ever named and there is no explicit 'use set_project_bumpers instead when...' routing. The agent must infer the clip-vs-project split from the description alone.

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