Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

overwrite_from_source

Replace the current clip in the timeline with the clip from the Source Monitor at the playhead position. Specifies target video and audio track indices.

Instructions

Overwrite the clip from the Source Monitor at the playhead position (overwrite edit — replaces existing clips).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_track_indexNoTarget video track index (default: 0)
audio_track_indexNoTarget audio track index (default: 0)
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It mentions 'replaces existing clips' but omits details like prerequisites (e.g., must have a source clip open in Source Monitor), potential data loss, or error conditions. The description is insufficiently transparent.

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 description is a single sentence that efficiently conveys the core functionality without extraneous words. It is well-structured and front-loaded.

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?

Given no output schema and no annotations, the description should provide more context about the tool's behavior, prerequisites, and post-conditions. It lacks completeness for a destructive timeline edit operation.

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% with descriptions for both parameters (video_track_index, audio_track_index). The tool description adds context by linking to overwrite edit and source monitor, but does not significantly enhance understanding beyond the schema. Score is at the baseline for high coverage.

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), the source (Source Monitor), the location (playhead position), and the effect (replaces existing clips). It is specific and distinguishes from sibling tools like 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?

The description does not provide any guidance on when to use this tool versus alternatives such as insert_from_source or overwrite_clip. It lacks explicit context or exclusions, leaving the agent to infer usage.

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