Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

replace_clip_media

Replace a timeline clip's source media with a different project item while preserving its position and duration.

Instructions

Replace the source media of a clip on the timeline with a different project item, keeping the clip's position and duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clip_node_idYesNode ID of the timeline clip to replace media on
new_item_idYesNode ID or name of the new source project item
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It mentions keeping position and duration but omits details on effects, speed, compatibility requirements, or what happens if the new media has a different length.

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?

The single sentence is concise, front-loaded with the action, and contains no unnecessary words.

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

Completeness3/5

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

The tool has two required parameters and no output schema. The description explains the core function but does not mention return value, success/failure indicators, or prerequisites (e.g., clip must exist in timeline).

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?

The input schema has 100% description coverage for both parameters, so the description adds no extra meaning beyond the schema. The description does not provide examples or guidance on obtaining node IDs.

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 (replace source media) and the resource (clip on a timeline), with the specific constraint of keeping position and duration. This distinguishes it from sibling tools like 'replace_clip' or 'overwrite_clip'.

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 the tool is used when you want to swap media while preserving timeline properties, but it does not explicitly state when to use or when not to use it, nor does it mention alternatives among siblings.

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