Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Detect Silence

detect_silence

Analyse a media file to find silent ranges and the loud segments worth keeping. Read-only ffmpeg analysis; nothing in the project is modified.

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
NameRequiredDescriptionDefault
media_pathNoAbsolute path to the media file to analyse. Provide this or project_item_id.
project_item_idNoNode ID or name of a project item whose media path is resolved through Premiere. Provide this or media_path.
noise_threshold_dbNoLevel at or below which audio counts as silence, in dBFS. Closer to 0 is more aggressive (default: -30).
min_duration_secondsNoShortest run of silence to report, in seconds (default: 1.5).

Output Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • 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."
  2. Changed2 schema fields changedv1.14.4
    • 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"
+}
  3. Addedv1.8.0

TDQS

A3.7/5.0
Behavior2/5

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

The description adds real context — analysis-only semantics, the ffmpeg dependency, and the rationale that Premiere's scripting API exposes no waveform data. However it asserts the tool modifies nothing, while annotations declare readOnlyHint=false and idempotentHint=false, so the agent receives conflicting signals about whether any state changes. The rationale for that mismatch (e.g. temp-file writes by ffmpeg) is not spelled out.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the outcome and scope, then the safety statement, then the dependency and its reason. Every sentence carries information, though the dependency clause is slightly dense and could be split for faster scanning.

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?

An output schema exists, so return values need not be explained, and the description covers scope, mutation safety, and environment prerequisites. The remaining gap is routing — it does not tell the agent which sibling to prefer for downstream silence handling — plus the unresolved tension with the readOnly annotation.

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% and each parameter is documented with type, purpose, and default (noise_threshold_db -30 dBFS, min_duration_seconds 1.5s, and the media_path/project_item_id either-or). The description adds no parameter-level detail beyond that, so the baseline of 3 is appropriate.

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 ('Find silent ranges in a media file') and goes further by declaring the dual return ('both the silences and the complementary segments worth keeping'). This cleanly separates it from planning-oriented siblings such as plan_silence_review_markers and plan_pause_tightening, which act on the timeline rather than the raw media file.

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?

Clearly bounds the tool as read/analysis-only ('nothing in the project or on the timeline is modified') and states an environmental prerequisite ('Requires ffmpeg on PATH'), which tells the agent when the call will even succeed. It stops short of explicitly naming which sibling to use instead when the goal is marker placement or pause tightening, so the routing guidance is implicit rather than explicit.

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