Skip to main content
Glama

select_clips_by_color

Identifies and selects all clips of a specified color in a Premiere Pro timeline, enabling targeted batch operations like editing, filtering, or organizing footage.

Instructions

Premiere Pro expanded operation: select clips by color.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does not say whether the current selection is replaced or extended, whether it targets clips in the active sequence or bin, what 'by color' means (label color vs luminance), or what requirements exist (e.g., active sequence).

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

Conciseness4/5

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

At seven words, the description is very concise. However, 'Premiere Pro expanded operation' adds little value since all sibling tools are Premiere Pro operations, and the phrase 'expanded operation' is unexplained filler.

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?

The description is insufficient for a selection tool with no annotations and no output schema. It leaves critical gaps: the selection scope (active sequence vs bin), selection mode (additive vs replace), and the meaning of 'by color' are all unspecified.

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 tool has zero parameters and the schema is empty (additionalProperties: true). With no parameters to document, the description does not need to compensate, and the baseline is 4.

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

Purpose4/5

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

The description states a specific verb and resource: 'select clips by color.' This distinguishes it from sibling tools like select_clips_by_name and select_clips_in_range. The phrase 'expanded operation' is vague filler but does not obscure the core function.

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 usage guidance is provided. There is no mention of when to prefer this over siblings such as select_clips_by_name or select_clips_in_range, and no exclusions or prerequisites are stated. The description only restates the basic function.

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