Skip to main content
Glama
Cut Review

Cut Review

by DareDev256

edit

Modify clips on the timeline by inserting, deleting, trimming, splitting, reordering, retiming, removing silence, or attaching audio, B-roll and transitions, writing a new FCPXML file.

Instructions

Change clips on the timeline: insert, delete, trim, split, reorder, retime, remove silence, and attach audio, B-roll or transitions. Writes a new file. Actions: insert_clip, delete_clips, trim_clip, split_clip, reorder_clips, change_speed, rapid_trim, add_transition, add_audio, add_connected_clip, assign_role, fill_gaps, fix_flash_frames, remove_silence_candidates, remove_media_silence, set_keyframes, delete_keyframes, batch_keyframes, set_animation_curve, set_speed_curve, reset_speed.

Input Schema

NameRequiredDescriptionDefault
argsNoArguments for the chosen action, e.g. {"filepath": "/path/to/project.fcpxml"}. Any action that takes a filepath also accepts expected_sha256: the call refuses if the file no longer hashes to it (every write result and analyze_timeline report the current sha256).
actionYesWhich operation to run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool 'Writes a new file', implying the source is not mutated in place, which is the single most important behavioral trait for a write tool. It says nothing about failure/refusal behavior, overwrite safety, ripple side effects, or that actions differ widely in destructiveness, so the disclosure is partial.

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 in the first clause and the write behavior is stated early, before the enumeration. The 21-item action list is long and duplicates the schema enum, but for a mega-tool that breadth is defensible for agent routing, so it stays tight overall.

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

Completeness3/5

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

This is a 21-action, deep-nested, no-output-schema tool where the description covers only the umbrella purpose and the action roster. The rich schema compensates for parameter detail, but cross-action context (which actions produce new files vs modify in place, typical sequencing, expected results) is left entirely unstated.

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% and the schema is unusually rich, including per-action conditionals and detailed field docs, so the baseline is 3. The description's action enumeration merely restates the schema enum and adds no parameter meaning beyond what the schema already carries.

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 ('Change clips on the timeline') and enumerates the operation categories plus every action name, so an agent can tell this is the mutation umbrella tool. It does not explicitly contrast with siblings like organize or generate, which could plausibly also alter a project, so it stops short of 5.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance, no prerequisite sequencing (e.g. that clip_path must come from a prior inspect.list_keyframes call, which only surfaces in the schema), and no routing between the 21 actions. 'Writes a new file' is a behavioral fact, not usage guidance, so an agent gets little help choosing this tool over its siblings.

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