Remove a video or audio track from the active Premiere Pro sequence by specifying track type and index.
Remove a track from the active sequence
| Name | Required | Description | Default |
|---|---|---|---|
| trackType | Yes | Track type | |
| trackIndex | Yes | Track index to remove |
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 states that a track is removed, but it does not disclose whether clips on the track are also removed, whether the action is reversible, or any constraints such as minimum track requirements.
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. It states the essential action and scope 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?
The tool is a mutation with no annotations and no output schema, so the description needs to compensate for missing safety and behavioral context. It does not explain destructive side effects, reversibility, or track-removal constraints, leaving meaningful gaps for an agent deciding whether and how to invoke it.
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%, and the schema already documents trackType as an enum of video/audio and trackIndex as the index to remove. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.
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 names a specific verb and resource ("Remove a track") and scopes it to the active sequence. It is clearly distinguishable from sibling tools such as add_tracks and remove_clip without needing to inspect the schema.
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 description implies when the tool applies by stating it removes a track from the active sequence, but it does not explicitly say when to use it versus alternatives or note any prerequisites. This is adequate implied guidance rather than explicit usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.