Skip to main content
Glama

set_best_cut

Mark the chosen cut range for a storyboard take after verifying the suggested cut with the transcript and frames. The user sees it in the Storyboard tab; call cut_take to make the clip.

Instructions

Set the best cut of a storyboard take after you checked it. The best_cut from Gemini (or from the transcript, without a key) is only a first suggestion: compare it with the transcript and the frames, then write the range you use here (by=agent; the first range stays under gemini). The user sees it on the take in the Storyboard tab. This only marks a range. To make the clip, call cut_take with that range.

Input Schema

NameRequiredDescriptionDefault
endYesSeconds from the start of the take.
whyYesOne short sentence: what you checked, and what you changed.
saidNoWhat the user says in the range, word for word.
takeYesTake number.
cleanNoEvery word of the shot's lines is there. Default true.
startYesSeconds from the start of the take.
sessionYesSession as 'Project/folder', an absolute path, or its id (from get_session). An old path still works after a rename or move.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-readonly/non-destructive; the description adds real value beyond them by clarifying 'This only marks a range' (no clip is produced) and that the user sees it on the take in the Storyboard tab. It doesn't cover auth or failure behavior, but for this tool that's a minor gap.

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?

Purpose is front-loaded and each sentence earns its place (verification, Gemini comparison, visibility, hand-off to cut_take). It is somewhat long at five sentences but none is pure 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?

No output schema, but the annotations plus description cover the safety profile, the downstream effect (user-visible range), and the follow-up call. An agent has everything needed to invoke it correctly; only edge/error behavior is unaddressed.

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%, so all seven parameters are already documented. The description reinforces the intent of start/end ('write the range you use') but adds no syntax or format detail beyond the schema; 'by=agent' is not a schema parameter, so it contributes little to invocation semantics.

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 ('Set the best cut of a storyboard take') and immediately frames it against the Gemini/transcript suggestion, so an agent distinguishes it from cut_take 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 Guidelines5/5

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

Explicitly says when to use it ('after you checked it', 'compare it with the transcript and the frames'), what it is not ('only a first suggestion'), and names the follow-up alternative ('To make the clip, call cut_take with that range'). 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.