Remove a clip from the Premiere Pro timeline using a lift edit, with an option to ripple delete and close the gap.
Remove a clip from the timeline (lift edit)
| Name | Required | Description | Default |
|---|---|---|---|
| ripple | No | If true, ripple delete (close the gap). Default: false | |
| clipIndex | Yes | Clip index | |
| 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 carries the full behavioral burden. It indicates a removal and lift-edit gap behavior, but does not explain destructive consequences, linked clips, permissions, reversibility, or expected response.
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 definition is a single front-loaded sentence with no wasted words. It communicates the core operation immediately.
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 simple timeline edit with fully documented parameters, the description is adequate to identify the operation. However, with no annotations or output schema, it should do more to explain alternatives and mutation consequences.
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%, including the ripple flag and required track/clip indexes. The description adds only the "lift edit" framing and does not provide parameter-level detail beyond what the schema already documents.
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: removing a clip from the timeline. The parenthetical "lift edit" adds useful distinction by implying the default leaves a gap, though it does not explicitly name the sibling ripple_delete.
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?
There is no explicit guidance on when to use this tool versus alternatives such as ripple_delete or razor_clip. Usage is only implied by the operation name, and the ripple distinction is left to the parameter schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.