Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

select_clips_in_range

Select all clips that overlap a specified time range in the active Premiere Pro sequence.

Instructions

Select all clips that overlap a time range in the active sequence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_typeNoTrack type (default: both)
end_secondsYesEnd of selection range in seconds
track_indexNoSpecific track index (optional)
start_secondsYesStart of selection range in seconds
Behavior2/5

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

The description does not disclose important behavioral traits such as whether the selection replaces or adds to the current selection, or any side effects like scrolling or highlighting. Annotations are all false and provide no extra context, so the burden is on the description.

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

Conciseness5/5

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

The description is a single, concise sentence that efficiently communicates the tool's core functionality without any unnecessary words.

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

Completeness3/5

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

For a selection tool with 4 parameters and no output schema, the description is adequate but lacks explanation of overlap semantics, behavior with no clips, or interaction with the current selection. It covers the basic purpose but leaves gaps for an agent.

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

Parameters3/5

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

All parameters are fully described in the input schema, so the description adds no additional meaning beyond what the schema already provides. This meets the baseline for high schema_description_coverage (100%).

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

Purpose5/5

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

The description clearly states the verb 'Select', the resource 'clips', and the specific criterion 'that overlap a time range in the active sequence'. This distinguishes it from sibling selection tools like select_clips_by_name or select_all_clips.

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

Usage Guidelines3/5

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

The description implies usage when a time-range-based selection is needed, but it does not provide explicit guidance on when to use this tool versus alternatives like select_clips_by_name or select_all_clips. There is no mention of prerequisites or exclusion criteria.

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

Install Server

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/leancoderkavy/premiere-pro-mcp'

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