Premiere Pro MCP Server

Detect Silence

detect_silence

Find silent ranges in a media file and get both the silences and the complementary segments worth keeping, enabling precise cut points without modifying the project.

Instructions

Find silent ranges in a media file and return both the silences and the complementary segments worth keeping. Analysis only — nothing in the project or on the timeline is modified. Requires ffmpeg on PATH: Premiere's scripting API exposes no audio-level or waveform data, so silence cannot be measured through the bridge.

Input Schema

TableJSON Schema

Name	Required	Description
`media_path`	No	Absolute path to the media file to analyse. Provide this or project_item_id.
`project_item_id`	No	Node ID or name of a project item whose media path is resolved through Premiere. Provide this or media_path.
`noise_threshold_db`	No	Level at or below which audio counts as silence, in dBFS. Closer to 0 is more aggressive (default: -30).
`min_duration_seconds`	No	Shortest run of silence to report, in seconds (default: 1.5).

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.

Changed2 schema fields changedv1.14.4Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}

Addedv1.8.0Aug 2, 2026

TDQS

A3.6/5.0

Behavior1/5

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

The description states 'Analysis only — nothing in the project or on the timeline is modified,' but the annotations declare readOnlyHint=false. This directly contradicts the annotation, so the behavioral transparency score must be 1 per the contradiction rule.

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 no wasted words: the first covers purpose and output, the second covers safety and the external ffmpeg dependency. Information is front-loaded and each sentence earns its place.

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?

The description covers the core details: what the tool does, that it is analysis-only, and why ffmpeg is required. The schema covers parameter semantics and defaults. The only gap is the readOnlyHint contradiction, which creates some confusion but does not prevent correct invocation.

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?

All four parameters have thorough descriptions in the schema (100% coverage), so the baseline is 3. The tool description does not add additional parameter-level meaning beyond the schema, which is acceptable given the schema's completeness.

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?

Description states a specific verb ('Find'), a clear resource ('silent ranges in a media file'), and the exact output ('both the silences and the complementary segments worth keeping'). This clearly distinguishes it from sibling analysis tools like analyze_loudness or plan_silence_review_markers.

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 strong context: it is analysis-only and requires ffmpeg because Premiere's bridge exposes no audio-level data. This tells an agent when this tool is necessary, though it does not explicitly name alternative tools or state 'use X instead when...'.

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

Deploy Server