Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

rename_clip

Renames a clip on the Premiere Pro timeline by providing its node ID and the new name.

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?

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond 'Uses QE DOM', which is an implementation detail. It does not describe error behavior (e.g., invalid node_id), side effects, or whether renaming is reflected immediately.

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 very concise with one clear sentence. The addition of 'Uses QE DOM' is somewhat redundant but does not detract. Front-loaded with the primary 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 required parameters and no output schema, the description adequately defines the core action. However, it could mention that the clip must be on the timeline and hint at how to obtain the node_id, which would improve completeness for an AI agent.

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 coverage is 100% and both parameters have descriptive names and descriptions ('Node ID of the clip', 'New name for the clip'). The description adds no additional meaning, so baseline score of 3 is appropriate.

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 'Rename a clip on the timeline' with a specific verb and resource. It distinguishes from sibling tools like 'rename_project_item' which renames project items, and 'batch_rename_clips' which operates on multiple clips, making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives like 'rename_project_item' or 'batch_rename_clips'. It does not mention prerequisites (e.g., clip must be on timeline, node_id obtained from other tools) nor scenarios where it should be avoided.

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