Skip to main content
Glama

Plan Word Mute Ranges

plan_word_mute_ranges
Read-onlyIdempotent

Plan mute or bleep ranges for specified words in a word-timed transcript, returning frame-snapped mute ranges and ready-to-apply audio keyframes plus bleep tone placements without changing 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.

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": {
      "word_timeline": "<word_timeline>",
      "words": "<words>"
    },
    "name": "plan_word_mute_ranges"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNomute ducks the dialogue only; bleep also emits tone placements. Defaults to mute.
wordsYesExact words or phrases to mute, matched as consecutive normalized tokens.
frame_rateNoTimebase used to snap ranges to whole frames; defaults to 30.
mute_level_dbNoLevel inside each range for add_audio_keyframes; defaults to -60.
word_timelineYesCaller-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_secondsNoSeconds added before and after each flagged word; defaults to 0.04.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A3.8/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 reinforces this with 'Local-only; never changes Premiere' plus a concrete summary of what the plan returns. It stops short of explaining the CEP-only guard parameters (expected_cep_target, expected_project_path) that will cause refusals, which is meaningful behavior left to the schema.

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 short sentences with no waste: purpose first, outputs second, safety/scope last. Every sentence carries information an agent needs.

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 an output schema present, return values needn't be spelled out, and the description still sketches the returned artifacts and the non-mutating guarantee. The main gap is the absent prerequisite/routing information (which transcript tool supplies word_timeline, which tool applies the plan).

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 parameters are already well documented and baseline 3 applies. The description adds only light meaning ('frame-snapped' implying frame_rate, the mute-vs-bleep distinction) that largely restates the schema.

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?

Specific verb + resource: 'Plan mute or bleep ranges for listed words/phrases in a word timeline', with the output artifacts named (redacted, frame-snapped ranges, audio keyframes, tone placements). It implicitly separates itself from apply-side siblings like add_audio_keyframes by noting the keyframes are only 'ready-to-apply', but it never names an alternative tool explicitly.

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 gives context ('Local-only; never changes Premiere') but no explicit when-to-use vs when-not guidance and no pointer to siblings such as add_audio_keyframes or plan_filler_word_removal. The prerequisite that the word_timeline must come from get_clip_transcript_uxp appears only in the schema, not the description.

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