Premiere Pro MCP Server

Plan Reaction Captions

plan_reaction_captions

Read-onlyIdempotent

Plan stacked, speaker-colored reaction captions from word-timed transcripts and a speaker palette, merging flash words and handling overlaps without altering Premiere.

Instructions

Plan stacked, speaker-colored reaction captions from a word timeline and an explicit speaker palette. Flash-length words merge, overlaps stack, and unknown speakers stay uncolored. Local-only; never changes Premiere.

Input Schema

TableJSON Schema

Name	Required	Description
`frame_rate`	No	Sequence frame rate used to snap times to frames; defaults to 30.
`shot_changes`	No	Optional labeled cut points. A matching speaker's caption will not start before they appear on screen when a readable hold remains.
`word_timeline`	Yes	Caller-supplied word-timed transcript for one Premiere source item. Words must be ordered by start time and bound to the transcript revision returned by get_clip_transcript_uxp. Different labeled speakers may overlap; same-speaker words may not, even when another speaker is between them.
`speaker_palette`	Yes	Known speakers and their exact #RRGGBB colors. Missing labels are returned as uncertain and never receive a guessed color.
`min_hold_seconds`	No	Minimum duration kept after clamping a cue to a shot change; defaults to 0.35.
`merge_gap_seconds`	No	Same-speaker words closer than this become one cue; defaults to 0.12 so a short pause can start a new line.
`combine_gap_seconds`	No	Maximum gap when combining a flash cue with the next same-speaker cue; defaults to 0.8.
`min_solo_cue_seconds`	No	Cues shorter than this merge with the next same-speaker cue; defaults to 0.45.

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.16.0Sep 16, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral specificity: 'Local-only; never changes Premiere' reinforces the read-only safety profile, while detailing merge, stacking, and uncolored-unknown-speaker behaviors goes well beyond annotation basics.

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 with zero wasted words. The main purpose is front-loaded, followed by key behavioral traits and a safety guarantee. Every sentence earns its place.

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

Completeness5/5

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

Given an output schema and 100% schema description coverage, the description covers the essential context: purpose, core behaviors, and local-only safety. Remaining details, such as the transcript_revision prerequisite, are already in the schema. No critical information is missing.

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 the schema fully documents all eight parameters. The description names the two primary inputs (word timeline, speaker palette) but adds no additional syntax or format details. With full schema coverage, the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Plan stacked, speaker-colored reaction captions' with explicit inputs. It also names distinct behaviors (flash-length words merge, overlaps stack, unknown speakers stay uncolored) that differentiate it from sibling planning tools without needing to name them.

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 implies usage context (when you have a word timeline and speaker palette for reaction captions) but does not explicitly state when to use it versus alternatives, nor does it mention exclusions or compare to sibling tools like plan_speaker_checkerboard or plan_beat_montage.

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

Deploy Server