premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Get Bridge Telemetry

get_bridge_telemetry

Read-onlyIdempotent

Inspect bridge health and diagnose whether the CEP bridge is blocked via queue age, busy operations, heartbeat state, and next steps. Use after timeouts or before retries when dialogs block scripting.

Instructions

Read-only, sends no command: inspect privacy-preserving aggregate bridge health (pending command/response counts, busy operations, queue age, CEP heartbeat state) and diagnose whether the CEP bridge is blocked. Use it after a timeout or before retrying: a modal dialog such as Missing Media blocks Premiere's scripting engine, so a probe script cannot run. blocking.state is idle, busy, likely_blocked_by_dialog, stuck, connector_not_running, or unknown, with reason, ages in ms, queued counts, the running tool name when known, and nextSteps. It reads only heartbeat and busy-marker timing; no OS window probe is performed (macOS needs Accessibility permission and window titles can name media), and no dialog is dismissed. Returns no paths, file names, or script contents.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_bridge_telemetry"
  }
}

Input Schema

Name	Required	Description
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_command_ms`	No	How long the in-flight command is expected to take, in ms (default: the bridge timeout, 30000). A command still running past this while the panel is alive is reported as likely_blocked_by_dialog. Raise it for long exports.
`expected_project_path`	No	Optional 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

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present 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.

First observedv1.30.0Nov 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds real value on top: it states no command is sent, no OS window probe is performed (with the macOS Accessibility permission and media-name-in-window-title rationale), no dialog is dismissed, and no paths/file names/script contents are returned. It also enumerates the blocking.state machine (idle, busy, likely_blocked_by_dialog, stuck, connector_not_running, unknown) and the accompanying reason/ages/queued/running tool/nextSteps fields.

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?

Front-loaded with the read-only guarantee and purpose, then usage, then the state enumeration, then privacy limits — a logical order with no filler sentences. It is dense and long-ish for a telemetry tool, but each sentence carries distinct information an agent would otherwise have to guess.

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?

For a nested-object, zero-required-parameter diagnostic with an output schema, the description covers purpose, trigger conditions, the full state vocabulary, timing fields, and privacy constraints. Nothing an agent needs to decide whether and how to call this is missing; return-value structure is delegated to the output schema as intended.

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 all three parameters are already fully documented in the schema, which sets the baseline at 3. The description adds no parameter-level guidance of its own — expected_command_ms, expected_cep_target, and expected_project_path are never mentioned, so the timeout tuning hint ('Raise it for long exports') exists only in 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 (inspect/diagnose) against a specific resource (CEP bridge health / blocked bridge) and enumerates exactly what is measured: pending command/response counts, busy operations, queue age, CEP heartbeat state. Distinct from every sibling because none of them read bridge telemetry; an agent can identify the tool without opening the schema.

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?

Gives explicit triggering conditions: 'Use it after a timeout or before retrying' and explains the underlying failure mode (a modal dialog blocks Premiere's scripting engine so probe scripts cannot run). It does not name the sibling diagnostics it supersedes in the blocked case (ping, verify_premiere_connection, can_execute, get_premiere_state), so ranking against alternatives is left to inference.

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

Deploy Server