Remove a transition from a video or audio track in Premiere Pro by specifying the track type, track index, and transition index retrieved from the track's transition list.
Remove a transition (index from get_transitions for that track)
| Name | Required | Description | Default |
|---|---|---|---|
| trackType | Yes | Track type | |
| trackIndex | Yes | Track index, 0-based (V1 = 0, A1 = 0) | |
| transitionIndex | Yes |
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 full behavioral burden. It identifies the action as a removal (mutation) but does not disclose side effects, reversibility, required permissions, or return behavior. Only the parameter sourcing is clarified.
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, front-loaded sentence with zero waste. It delivers the core action and the key parameter sourcing hint efficiently.
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 three parameters and no annotations or output schema, the description is minimally adequate. It covers the core action and parameter sourcing but omits usage alternatives and behavioral details that would aid correct invocation.
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 67% (trackType and trackIndex described; transitionIndex not). The description compensates by explaining that transitionIndex comes from get_transitions for that track, adding meaning beyond the schema for the undocumented parameter.
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 ('Remove a transition') and references the complementary tool 'get_transitions' for obtaining the index. Clear but does not explicitly differentiate from sibling tools like apply_transition beyond the implied workflow.
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?
Implies usage by mentioning 'index from get_transitions for that track,' indicating you need to fetch the index first. However, it does not state when to use this tool versus alternatives (e.g., apply_transition, remove_effect) or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.