Premiere Pro MCP Server

Preview Mogrt Premiere Handoff

preview_mogrt_premiere_handoff

Read-onlyIdempotent

Preview a MOGRT inside a disposable Premiere sequence before import. Verify the artifact imports correctly without altering your project or contacting Premiere.

Instructions

Preview a contained MOGRT import into one explicitly named disposable Premiere verification sequence and empty video track. It does not contact Premiere or alter a sequence.

Input Schema

TableJSON Schema

Name	Required	Description
`mogrt_path`	Yes	Existing workspace-contained MOGRT artifact.
`sequence_id`	Yes	Exact Premiere sequence identifier to recheck before import.
`start_seconds`	No	Insertion start time in seconds; defaults to 0.
`audio_track_index`	No	Audio track index passed to Premiere; defaults to 0.
`video_track_index`	No	Empty video track index for the imported MOGRT; defaults to 0.
`approved_workspace_path`	Yes	Absolute operator-approved workspace root.
`disposable_sequence_name`	Yes	Must begin with 'MOGRT Verify - '.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.14.9Sep 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/destructive. The description adds valuable context beyond annotations: it does not contact Premiere and does not alter a sequence, clarifying what 'preview' means in this tool's workflow. No contradiction with annotations.

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, front-loaded with the core operation, and the clarifying exclusion in the second sentence. No filler or redundancy.

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?

Combined with a fully described schema and an output schema, the description gives an agent enough to decide when to use the tool. Slight ambiguity remains around the relationship between 'does not contact Premiere' and the sequence_id being rechecked, but this is minor.

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%, so schema carries the parameter meaning. The description adds only light context (contained, explicitly named, empty video track) that largely mirrors schema property descriptions; it does not deepen parameter semantics.

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?

States a specific verb (Preview), resource (contained MOGRT import into one disposable Premiere verification sequence and empty video track), and explicitly excludes mutation/contact. Even without naming a sibling, the 'does not contact Premiere or alter a sequence' clause separates it from apply/handoff tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description establishes clear context: use for a non-destructive preview of a single MOGRT into a disposable sequence. It does not explicitly name alternative tools like apply_mogrt_premiere_handoff, but the exclusions communicate when not to use it.

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

Deploy Server