Selects specific video or audio clips on the Premiere Pro timeline by track and clip index so you can target them for subsequent editing operations.
Select specific clips on the timeline (for use with other operations)
| Name | Required | Description | Default |
|---|---|---|---|
| clips | Yes | Array of clip locations to select |
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 does not disclose whether existing selection is replaced or extended, whether an active sequence is required, what happens with invalid indices, or whether the selection persists.
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 filler. Its brevity contributes to readability, though the parenthetical is a missed opportunity to add real guidance.
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 selection-mutating tool with no annotations and no output schema, the description is too thin. An agent lacks essential context about selection state behavior, active-sequence requirements, and how this integrates with the many sibling operations that act on selected clips.
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 nested clips array and trackType enum are already documented in the schema. The description adds only the generic concept of 'specific clips' and does not clarify coordinate semantics beyond what the schema provides.
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: selecting clips on the timeline. It is clear what the tool does, but it does not distinguish this from related selection tools like deselect_all or get_selection.
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 parenthetical 'for use with other operations' hints that selection is a prerequisite for later actions, but it names no alternatives or specific follow-up tools. It does not explain when to use this versus deselect_all, get_selection, or other clip-targeting tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.