Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

overwrite_clip

Place a project item onto a chosen timeline track at a specific time, replacing existing content and verifying the new source location.

Instructions

Overwrite a project item onto validated timeline tracks and verify a new source placement at the requested time

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)
Behavior2/5

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

No annotations were provided, so the description bears the full burden. It mentions 'overwrite' but doesn't explain the destructive nature (replacing existing clips), whether the operation is reversible, or what 'validated' means in terms of checks. This is vague for a mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it wastes words on 'validated' without explaining it. Front-loads the action but lacks critical details. Not overly long, but could be more informative.

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 annotations. The description doesn't mention return values, success/failure behavior, or preconditions. Given this is a mutation tool with 4 paramsainer and no contextual overlays, the description is insufficient for an agent to use safely.

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?

All 4 parameters have descriptions in the schema. The description adds 'validated' but doesn't clarify parameter interactions (e.g., what happens if track_index is out of range). The schema already provides the basics, so the description adds marginal value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool overwrites a clip onto timeline tracks and verifies placementretical, which matches the name 'overwrite_clip'. However, 'validated' is ambiguous and doesn't clarify what validation is performed, slightly reducing clarity.

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 prerequisites or context are given. The description doesn't specify whether an active sequence is required, what happens if the track is null, or how this differs from similarly named tools like 'overwrite_from_source'. No guidance on when to use this over other timeline editing tools.

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