Cuts every unlocked track at once at a specified time, replicating Premiere Pro's Add Edit to All Tracks command for synchronized multi-track editing in a single step.
Cut every unlocked track at a time (like Add Edit to All Tracks)
| Name | Required | Description | Default |
|---|---|---|---|
| time | Yes | Seconds |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose that locked tracks are excluded, which is useful behavior, but it says nothing about whether cuts are undoable, whether clips under the playhead must exist, or what happens when no tracks meet the criteria.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with the operation and scope front-loaded, plus a recognizable analogue. Nothing wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with zero annotations and no output schema, the definition covers the what but not the consequences or return behavior. An agent knows what the call does but not whether it needs selection state or how to verify the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter with 100% schema coverage ('time', in seconds). The description adds no format or interpretation detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource combination: cutting every unlocked track at a given time. The scope qualifier 'every unlocked track' implicitly separates it from razor_clip, but it never names the sibling to make the distinction explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The parenthetical 'like Add Edit to All Tracks' anchors it to a known NLE operation, implying bulk/global use versus single-clip razor. There is no explicit statement of when to prefer it over razor_clip, nor any prerequisite such as an open sequence or active timeline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.