Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

batch_rename_clips

Rename multiple clips on the timeline with a pattern like 'Scene_{n}' for sequential numbering. Optionally rename only selected clips or those on a specific track.

Instructions

Rename multiple clips on the timeline using a pattern. Supports sequential numbering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYesName pattern. Use {n} for sequential number, {name} for original name (e.g., 'Scene_{n}', '{name}_v2')
track_typeYesTrack type to rename clips on
track_indexYesTrack index (0-based)
start_numberNoStarting number for {n} placeholder (default: 1)
selected_onlyNoOnly rename selected clips (default: false, renames all on track)
Behavior3/5

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

Annotations do not indicate destructiveness or idempotency. The description mentions renaming but does not disclose whether changes are reversible or affect other clip properties. Moderate transparency.

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?

Two concise sentences covering the core purpose and key feature (sequential numbering), with no unnecessary words.

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

Completeness4/5

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

For a tool with 5 parameters and no output schema, the description adequately explains the pattern usage. Could mention that renaming is applied to the timeline specific to track type and index, but overall sufficient.

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?

Schema coverage is 100%, and the description provides additional clarity on the pattern parameter with examples, adding value beyond the schema.

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 action (rename multiple clips) and the method (using a pattern with sequential numbering). It distinguishes from single-clip rename operations.

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 batch renaming but does not explicitly state when to use this tool versus alternatives like rename_clip or other batch operations. No exclusions or context provided.

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