Split a video or audio clip at a specific time on a chosen track for precise timeline edits in Premiere Pro.
Split/razor a clip at a specific time
| Name | Required | Description | Default |
|---|---|---|---|
| time | Yes | Time in seconds to split the clip | |
| trackType | Yes | Track type | |
| trackIndex | Yes | Track index |
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 must carry the full behavioral burden. It says the clip is split at a time, but does not state whether the operation is destructive, whether it affects linked audio/video, what happens to the resulting clips, or what prerequisites are required.
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?
The description is a single, front-loaded sentence with no wasted words. For a simple timeline operation, this is appropriately concise.
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?
The schema is fully described and supplies all required parameters, but the description does not explain how the target clip is identified from track and time, nor does it cover mutation side effects. For a no-annotation clip-editing tool, this is only minimally complete.
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?
Schema description coverage is 100%, so the schema already documents `time`, `trackType`, and `trackIndex`. The description adds no additional parameter meaning beyond saying the split occurs at a specific time.
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?
The description states a specific verb and resource: 'Split/razor a clip.' It clearly describes a timeline clip-editing operation, though it does not explicitly distinguish itself from the sibling `razor_all_tracks` tool.
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?
It provides no guidance on when to use this tool versus alternatives such as `razor_all_tracks` or other clip-editing tools. The only usage hint is the phrase 'at a specific time,' which is already implied by the schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.