Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Place clip on timeline

premiere_place_clip

Place a media file onto a Premiere Pro timeline at a specified time and video track. Trim in/out points and choose overwrite or insert mode to control clip placement.

Instructions

Place a media clip on a video track at a given time (seconds). Imports the file if needed. Optionally trim with inSeconds/outSeconds. mode 'overwrite' (default) stamps over; 'insert' ripples later clips right. The clip's own audio is routed automatically.

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": {
      "mediaPath": "<mediaPath>"
    },
    "name": "premiere_place_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaPathYesAbsolute path to the media file.
videoTrackNoTarget video track, 1-based (default 1).
atSecondsNoStart time on the timeline in seconds (default 0).
inSecondsNoTrim: source in-point (seconds).
outSecondsNoTrim: source out-point (seconds).
modeNooverwrite (default) or insert (ripple).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses key behaviors: automatic file import, optional trimming, mode effects (overwrite vs ripple), and automatic audio routing. It omits error conditions, undo behavior, or prerequisites like project/sequence requirements.

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 two sentences, front-loaded with the core action, and free of fluff. Every sentence adds value.

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 description covers purpose, parameters, and modes, but lacks information on return values (e.g., success/failure), error handling, or prerequisites (e.g., active project/sequence). For a 6-parameter tool with no output schema and no annotations, this is a noticeable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value beyond the schema by explaining importing behavior for mediaPath, clarifying trim parameters with 'source in/out-point', and detailing mode effects. This adds meaningful context.

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 ('Place a media clip on a video track at a given time') using a specific verb and resource. It adds details about importing, trimming, and modes, distinguishing it from sibling tools like premiere_import_files.

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 description explains the two modes (overwrite vs insert) and their effects, providing context for when to choose each. However, it does not explicitly state when not to use this tool or mention alternatives (e.g., using add_title for different clip types).

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