Skip to main content
Glama

set_clip_selection

Select specific clips in an Adobe Premiere Pro timeline to target them for further editing, trimming, or export operations.

Instructions

Premiere Pro expanded operation: set clip selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that clip selection is set, offering no details about side effects, prerequisites, scope, or whether the selection replaces or augments the current selection.

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

Conciseness2/5

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

The description is extremely short, but brevity here is under-specification, not conciseness. 'Premiere Pro expanded operation' is filler, and the rest duplicates the tool name without earning its place.

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

Completeness1/5

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

The description is completely inadequate for a selection-related tool with many siblings. It does not clarify whether it acts on timeline clips, project items, or source clips, nor how it relates to other selection tools, leaving an agent unable to invoke it appropriately.

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 declares 0 parameters with 100% schema coverage, so the baseline of 4 applies. The description adds nothing about parameters, but this is acceptable when no parameters exist; however, additionalProperties: true is left unexplained.

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

Purpose2/5

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

The description 'Premiere Pro expanded operation: set clip selection' essentially restates the tool name without elaboration. It does not distinguish set_clip_selection from sibling tools like select_clips_by_name or select_all_clips, making it a tautology rather than a clear purpose.

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 use this tool versus alternatives such as get_selected_clips, select_clips_in_range, or deselect_all_clips. The phrase 'expanded operation' is vague and does not provide actionable context for selecting among sibling tools.

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