Skip to main content
Glama

select_all_clips

Select all clips in the Adobe Premiere Pro timeline to enable bulk edits or batch operations across the project.

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 carries the full burden. It only says 'select all clips' without disclosing whether the existing selection is replaced or extended, whether it applies to the active sequence, or how track targets are handled. This operation mutates selection state, so such details are important.

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 terse but includes the wasteful prefix 'Premiere Pro expanded operation:' which adds no value. The action 'select all clips' is direct and would be clearer without this 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 lacks essential context: it does not specify whether selection is cleared or additive, does not mention the active sequence, and does not indicate behavior regarding disabled clips or track targeting. Without annotations or an output schema, this minimal description is incomplete for a mutation tool.

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, making semantic ambiguity minimal. The schema is empty and fully covered, and the description need not elaborate on parameter syntax. A score of 4 reflects the baseline for no parameters.

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 clear verb and resource: 'select all clips'. It is distinct from siblings like 'deselect_all_clips' by the affirmative action, though it does not explicitly differentiate from 'select_clips_in_range' or 'select_disabled_clips'. The 'Premiere Pro expanded operation' prefix adds little but does not confuse the core meaning.

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 on when to use this tool versus alternatives such as 'select_clips_in_range' or 'select_disabled_clips'. There is no mention of prerequisites, intended context, or situations to avoid.

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/hetpatel-11/Adobe_Premiere_Pro_MCP'

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