Removes a transition from a clip edge in Premiere Pro by specifying the track type, track index, clip index, and start or end position.
Remove a transition from a clip edge
| Name | Required | Description | Default |
|---|---|---|---|
| position | Yes | Which edge to remove the transition from | |
| 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?
With no annotations, the description carries the full disclosure burden and falls well short: it does not say what happens if no transition exists at the edge, whether the operation is undoable, whether adjacent clip timing is affected, or whether it can fail. For a mutation tool this is a significant gap.
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?
One short sentence, front-loaded with verb and resource, with no filler. It is efficient but borders on under-specification rather than being genuinely tight prose.
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?
Low parameter complexity works in its favor, but a mutation tool with no annotations and no output schema needs to explain success/failure behavior and undo implications. The description supplies none of that.
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 coverage is 100%, with enums and descriptions covering all four parameters, so the baseline is 3. The phrase 'clip edge' loosely reinforces the position enum but adds no syntax, indexing convention, or zero-based/one-based detail beyond the schema.
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 uses a specific verb (remove) and resource (transition) anchored to a location (clip edge), so an agent can distinguish it from apply_transition or get_video_transitions_list. It stops short of naming those siblings explicitly, so the differentiation is good but not spelled out.
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 guidance on when to use this versus apply_transition or set_default_transition, and no mention of preconditions such as a transition actually existing at that edge. The agent must infer the calling context entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.