Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

duplicate_clip

Duplicates a selected clip on the Premiere Pro timeline, placing the copy immediately after the original or at a specified time offset for quick reuse.

Instructions

Duplicates a clip on the timeline.

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>"
    },
    "name": "duplicate_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYesThe ID of the clip to duplicate
offsetNoTime offset in seconds for the duplicate (default: places immediately after original)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, placing the full burden on the description. The phrase 'Duplicates a clip' implies a mutation but does not disclose side effects, return values, or whether the original is modified. This lack of behavioral context is a significant gap for a mutation tool.

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, focused sentence that is immediately understandable. It is appropriately sized and front-loads the core action without any fluff.

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 the low complexity (2 params, no output schema), the description could still be more informative. It omits any mention of what happens after duplication (e.g., selection, return value) and does not mention the default placement behavior of the duplicate, which is left entirely to the schema. The description is minimally adequate but not contextually complete.

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% (both clipId and offset have detailed descriptions). Per the rubric, this yields a baseline of 3. The tool description adds no extra parameter context beyond the schema.

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 uses a specific verb 'Duplicates' and a clear resource 'a clip', with scope 'on the timeline'. This clearly distinguishes it from siblings like 'duplicate_sequence' or 'copy_effects_between_clips'.

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 usage is implied by the clear purpose; an agent knows when to invoke it. However, there is no explicit guidance on alternatives, exclusions, or prerequisites, so it falls at the baseline for implied usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools