Skip to main content
Glama

select_clips_in_range

Selects clips within a specified timeline range in Adobe Premiere Pro, allowing you to target multiple clips for editing, cleanup, or export operations.

Instructions

Premiere Pro expanded operation: select clips in range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description is the only source of behavioral information, and it only says 'select clips in range'. It does not disclose whether the current selection is replaced, whether an active sequence is required, or what 'range' refers to, so an agent cannot predict the side effects of invoking it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but it is under-specified rather than concise; 'expanded operation' is filler that adds no actionable information. It is a single sentence, but it does not use the available space to convey necessary context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the large family of selection tools and the absence of annotations or output schema, the description is too sparse to enable correct invocation. It does not clarify what input is expected, what 'range' means, or how the behavior differs from related selectors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero documented parameters and 100% schema description coverage, so the description is not required to explain parameters. The baseline of 4 applies because nothing is missing at the parameter level, although the schema's additionalProperties: true is open-ended.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does name a specific action and resource - selecting clips within a range - and the 'range' wording loosely distinguishes it from sibling selectors like select_clips_by_name and select_all_clips. However, 'expanded operation' is opaque and the meaning of 'range' (time range, selection range, edit range) is undefined, leaving ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to prefer this tool over alternatives such as select_clips_by_name, select_clips_by_color, or select_all_clips. It does not state prerequisites, effects on existing selection, or which range context is used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tro2789/scout-premiere-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server