Skip to main content
Glama

Plan Silence Review Markers

plan_silence_review_markers
Read-onlyIdempotent

Plans review-only silence markers by mapping FFmpeg-detected source-media silences to a 1x timeline placement, clipping candidates to the source span and redacting paths without editing Premiere.

Instructions

Create a bounded, non-mutating review plan that maps FFmpeg-detected source-media silences onto one known 1x timeline placement. It clips candidates to the supplied source in/out span, redacts the source path, and never adds markers, cuts clips, or 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": {
      "media_path": "<media_path>",
      "timeline_start_seconds": "<timeline_start_seconds>"
    },
    "name": "plan_silence_review_markers"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_pathYesAbsolute path to the local source media file to analyse.
max_candidatesNoMaximum candidate ranges to return (default: 50, maximum: 200).
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
source_in_secondsNoSource-media in point used by the placement (default: 0).
noise_threshold_dbNoLevel at or below which audio counts as silence, in dBFS (default: -30).
source_out_secondsNoExclusive source-media out point used by the placement. Defaults to the detected media duration when available.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
min_duration_secondsNoShortest run of silence to consider (default: 1.5).
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.
timeline_start_secondsYesTimeline time where this 1x source placement begins.

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/5.0
Behavior4/5

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

The annotations already declare read-only, non-destructive, idempotent behavior, and the description reinforces this with specific guarantees: it clips candidates to the supplied source in/out span, redacts the source path, and never changes Premiere. It adds useful behavioral context beyond the annotations, though it does not cover every operational detail in 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?

The description is two tight sentences with the core action and key restrictions front-loaded. There is no redundant or filler language.

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?

For a complex planning tool with ten parameters, nested objects, and an output schema, the description provides enough core context to understand the tool's non-mutating planning role. The main gap is the absence of explicit routing guidance versus sibling detection or marker-creation tools.

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 already explains all ten parameters in detail. The description adds meaning about source in/out span and one known 1x timeline placement, but it does not elaborate on the other parameters such as max_candidates, noise_threshold_db, or idempotency_key.

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: creating a bounded, non-mutating review plan that maps FFmpeg-detected source-media silences onto one known 1x timeline placement. It also distinguishes the tool from marker-adding and editing tools by explicitly saying it never adds markers, cuts clips, or changes Premiere.

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 implied usage context: it is for building a review plan of silences without mutation. However, it does not explicitly say when to use this tool instead of siblings such as detect_silence, plan_chapter_markers, or add_markers_batch, leaving the agent to infer the choice.

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