Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

overwrite_clip

Overwrites existing timeline clips by placing a project item at a specified track and start time, instantly replacing the content at that position.

Instructions

Overwrite a project item onto the timeline (replaces existing clips at the insertion point)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesNode ID or name of the project item to add
track_indexNoVideo track index (0-based, default: 0)
start_secondsNoStart time in seconds on the timeline (default: 0)
audio_track_indexNoAudio track index (0-based, default: 0)
Behavior3/5

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

The description transparently states that the tool replaces existing clips, which aligns with its non-read-only annotation. However, annotations indicate destructiveHint=false, while replacement could be considered destructive; the description does not clarify undo capability or data loss risk.

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?

A single sentence that conveys the core purpose and effect. It is front-loaded and efficient, though it could be slightly improved with separation of action and effect.

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?

No output schema and no mention of return values or success/failure indicators. For a mutation tool, the description lacks information on what the agent can expect after invocation (e.g., confirmation, errors).

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 description coverage is 100%, so parameters are already well-documented. The description adds no further meaning beyond the schema, such as clarifying 'project item' or how to obtain item 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 ('Overwrite a project item onto the timeline') and the effect ('replaces existing clips at the insertion point'), distinguishing it from similar tools like 'add_to_timeline' or 'insert_from_source'.

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 versus alternatives, such as 'insert_from_source' or 'replace_clip'. The description does not mention prerequisites or context for appropriate use.

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