Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

rename_clip

Rename a clip on the timeline by providing its node ID and a new name. This tool uses QE DOM to directly modify clip names within Premiere Pro.

Instructions

Rename a clip on the timeline. Uses QE DOM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip
new_nameYesNew name for the clip
Behavior2/5

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

Description mentions 'Uses QE DOM' but does not disclose side effects, prerequisites, or constraints (e.g., whether clip must be selected, if rename is undoable). With no annotations, more detail is needed.

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 short sentences, 11 words, with no wasted information. Front-loaded with the core purpose.

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 simple rename operation with two string parameters and no output schema, the description adequately specifies the timeline context. However, could mention that it applies to the active sequence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond what the schema provides, so baseline score applies.

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) and resource (clip on timeline), distinguishing it from siblings like rename_bin, rename_project_item, and batch_rename_clips.

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 on when to use this tool vs alternatives such as batch_rename_clips or rename_project_item, which operate on similar but different resources.

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