Skip to main content
Glama

Plan Filler Word Removal

plan_filler_word_removal
Read-onlyIdempotent

Plan word-level filler removal from a revision-bound word timeline, returning frame-snapped removal and keep ranges plus apply routes without changing Premiere.

Instructions

Plan word-level filler removal (um, uh, you know...) from a revision-bound word timeline. Hesitation-sound removal requires a transcript that preserves disfluencies, such as Premiere transcription or verbatim ASR; Whisper's default output omits them. Returns frame-snapped removal and keep ranges plus apply routes. 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>"
    },
    "name": "plan_filler_word_removal"
  }
}

Input Schema

NameRequiredDescriptionDefault
frame_rateNoTimebase used to snap ranges to whole frames; defaults to 30.
filler_wordsNoFiller words or multi-word phrases to remove (matched as consecutive normalized tokens). Defaults to: um, uh, er, ah, hmm, you know, i mean, sort of, kind of. 'like' is only removed when listed explicitly.
max_removalsNoMaximum merged removals to return; defaults to 256.
handle_framesNoFrames of handle left inside each removal so cuts are not tight; defaults to 1.
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.
min_confidenceNoOptional: only remove fillers whose every word carries a confidence at or above this value.
merge_gap_secondsNoRemovals separated by less than this are merged into one cut; defaults to 0.15.
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

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds meaningful context beyond that: it is local-only, never changes Premiere, returns frame-snapped removal and keep ranges plus apply routes, and depends on a disfluency-preserving transcript.

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: purpose first, then the critical transcript prerequisite, then return and safety behavior. Every sentence adds useful information with no repetition or waste.

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, full schema descriptions, and strong annotations, the description covers the remaining agent-critical context: what it plans, the transcript prerequisite, that output includes removal/keep ranges and apply routes, and that it is local-only and non-mutating.

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 input schema already documents all nine parameters in detail. The description adds the important concept that the word timeline is revision-bound and must come from a disfluency-preserving transcript, but it does not add syntax or field-level semantics beyond the schema.

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 and resource: planning word-level filler removal from a revision-bound word timeline, with examples (um, uh, you know). It clearly distinguishes planning from mutation by saying it returns removal/keep ranges and apply routes rather than changing Premiere.

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?

Provides a clear prerequisite: the transcript must preserve disfluencies, such as Premiere transcription or verbatim ASR, because Whisper's default output omits them. It does not explicitly compare against close siblings like plan_word_mute_ranges or plan_pause_tightening, so it falls short of full when/when-not/alternatives guidance.

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