Premiere Pro MCP Server

Plan Word Mute Ranges

plan_word_mute_ranges

Read-onlyIdempotent

Plan mute or bleep ranges for specific words in a word-timed transcript, returning frame-snapped ranges, audio keyframes, and tone placements without altering Premiere.

Instructions

Plan mute or bleep ranges for listed words/phrases in a word timeline. Returns redacted, frame-snapped mute ranges, ready-to-apply audio keyframes and (for bleep) tone placements. Local-only; never changes Premiere.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	mute ducks the dialogue only; bleep also emits tone placements. Defaults to mute.
`words`	Yes	Exact words or phrases to mute, matched as consecutive normalized tokens.
`frame_rate`	No	Timebase used to snap ranges to whole frames; defaults to 30.
`mute_level_db`	No	Level inside each range for add_audio_keyframes; defaults to -60.
`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.
`padding_seconds`	No	Seconds added before and after each flagged word; defaults to 0.04.

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

changedInput schema / properties / word_timeline / description

Previous value: -"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."New value: +"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."

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 declare readOnly/idempotent/non-destructive, and the description meaningfully adds that it does not touch Premiere and that output is frame-snapped/redacted. It stops short of describing determinism or error behavior, but adds real context beyond structured fields.

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?

Three tight sentences, front-loaded with the purpose, then output, then the safety constraint. Every sentence earns its place with no 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?

With a rich output schema and full annotation coverage, the description needn't explain return values, and it still outlines them briefly. It is complete enough for correct invocation, though it could tie into the apply-step sibling for a fully rounded picture.

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 all six parameters including the mode enum and nested word_timeline are already documented. The description only echoes the mute-vs-bleep distinction without adding syntax or format 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (plan) and resource (mute/bleep ranges for listed words in a word timeline). The 'plan' framing clearly distinguishes it from execution siblings like mute_track and add_audio_keyframes, which actually apply changes.

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?

Makes the workflow context clear: it is a planning step whose output is 'ready-to-apply' keyframes, and it is 'local-only; never changes Premiere'. However it does not explicitly name the sibling to call afterward (e.g. add_audio_keyframes) or any when-not condition.

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

Deploy Server