Skip to main content
Glama

select_all_clips

Select all clips in the Adobe Premiere Pro timeline at once to enable batch editing and unified changes across the entire sequence.

Instructions

Premiere Pro expanded operation: select all clips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It only states the action, without explaining that selection is applied to the active timeline, whether the previous selection is replaced, or what happens if no sequence is active. This is a significant gap for a mutation-like tool.

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?

The description is only one short line, making it efficient and front-loaded. However, 'expanded operation' is filler that adds no meaningful information; trimming it would make the sentence cleaner.

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 tool is simple (0 params, no output schema), but the description lacks essential context about what scope 'all clips' refers to. Given the many sibling selection tools and the absence of annotations, the description is too minimal to fully guide an agent without guesswork.

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 takes zero parameters, so the schema imposes no burden. The description adds no parameter details because there are none to describe; baseline 4 is appropriate since the tool's operation is fully defined by its name and description.

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 the verb and resource clearly: 'select all clips.' It differentiates from siblings like select_clips_by_name and select_clips_in_range by indicating a broad, unfiltered selection. The phrase 'expanded operation' adds ambiguity but does not obscure the core 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 provided for when to use this tool versus alternatives such as select_clips_by_name or select_disabled_clips. There is no mention of scope (e.g., active sequence vs. bin) or contextual prerequisites, leaving the agent to infer usage.

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/compimprove/adobe-premiere-mcp'

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