MCP Premiere Pro

Overview Schema Source Related Servers Discussions Admin

replace_clip

Swap a timeline clip with a different media item while optionally preserving its effects and settings. Use it to update footage without rebuilding edits.

Instructions

Replaces a clip on the timeline with another media item.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clipId": "<clipId>",
      "newProjectItemId": "<newProjectItemId>"
    },
    "name": "replace_clip"
  }
}

Input Schema

Name	Required	Description
`clipId`	Yes	The ID of the clip to replace
`preserveEffects`	No	Whether to keep effects and settings (default: true)
`newProjectItemId`	Yes	The ID of the new project item to use

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Oct 23, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and does not mention side effects, whether the original clip is removed, or if any settings are affected. For a mutation tool, this is a significant lack of transparency.

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 one short, front-loaded sentence that efficiently conveys the core action with zero filler. It is appropriately concise for a simple operation.

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 is relatively simple with three parameters and no output schema. The description provides the essential action and all params are covered by the schema, but it lacks behavioral context such as effects of replacement or required state of the timeline, and it does not clarify differences from similar tools.

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 covers 100% of parameters with descriptions, so baseline is 3. The description itself adds no additional parameter meaning beyond the schema, but the schema fully documents clipId, preserveEffects, and newProjectItemId.

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 verb 'Replaces' and the resource 'clip on the timeline' with 'another media item', making the purpose specific. However, it does not differentiate from sibling tools like replace_clip_media or overwrite_clip, which could perform similar actions.

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 is provided on when to use this tool versus alternatives. The description gives no context about prerequisites, such as needing a valid clipId or newProjectItemId, or when this operation is preferable to 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.

Deploy Server