Premiere Pro MCP Server

Preview Motion Graphics Demo

preview_motion_graphics_demo

Read-onlyIdempotent

Preview a motion-graphics demo assembled from existing project items before applying changes. Use it to validate sequence layout without creating assets, importing files, or altering Premiere.

Instructions

Preview a contained motion-graphics demo assembly from existing project items. It never creates demo assets, imports files, creates a sequence, or changes Premiere; apply requires an exact confirmation token.

Input Schema

TableJSON Schema

Name	Required	Description
`sequence_id`	Yes	Exact ID of an existing empty destination sequence. It must be active at apply time.
`asset_item_ids`	Yes	Exact existing project-item node IDs in playback order; external media paths are deliberately not imported by this workflow.
`transition_name`	No	Transition name; defaults to Cross Dissolve. Use none to disable transitions.
`audio_track_index`	No	Empty destination audio track index, default 0.
`video_track_index`	No	Empty destination video track index, default 0.
`clip_duration_seconds`	No	Planned spacing between asset starts; defaults to 5 seconds for a motion demo and 4 seconds for spots.
`transition_duration_seconds`	No	Transition duration, default 0.75 seconds for demos and 0.5 seconds for spots.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.18.6Sep 30, 2026

changedOutput schema / properties / data / description

Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."

Changed1 schema field changedv1.14.9Sep 8, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Addedv1.14.4Aug 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope. The description adds value beyond them by enumerating what is NOT done (no asset creation, no import, no sequence creation, no Premiere mutation) and by noting the separate confirmation-token requirement at apply time.

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?

Two sentences, no filler. The purpose comes first, the negative scope and the apply-gate warning follow, in that priority order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 well-documented params, an output schema and rich annotations, the description needs only to frame intent and constraints, which it does. A little more on the preview→apply handoff would make it fully self-contained.

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 per-parameter descriptions covering the destination sequence, playback-order item IDs, transition defaults, track indices and durations. The description adds no parameter detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource: previewing a contained motion-graphics demo assembly built from existing project items. It also clarifies scope by negation ('never creates demo assets, imports files, creates a sequence'), which separates it from build/apply siblings. It stops short of naming the specific apply counterpart it precedes.

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 closing clause 'apply requires an exact confirmation token' implies this is the dry-run step of a preview→apply workflow, letting an agent infer when to use it. However, no sibling is named and there is no explicit 'use before X / not for Y' routing guidance.

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

Deploy Server