premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Analyze Loudness

analyze_loudness

Measure integrated loudness (LUFS), loudness range (LU), and true peak (dBFS) from local audio or video files using EBU R128 analysis, without normalizing audio or changing Premiere.

Instructions

Measure integrated loudness (LUFS), loudness range (LU), and true peak (dBFS) from a local media file using FFmpeg's EBU R128 filter. Analysis only: it does not normalize audio or change Premiere.

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": "analyze_loudness"
  }
}

Input Schema

Name	Required	Description
`media_path`	No	Absolute path to a local audio or video file. Provide this or project_item_id.
`target_lufs`	No	Optional delivery target in LUFS (for example -14 streaming, -16 podcast, or -23 broadcast)
`tolerance_lu`	No	Allowed absolute difference from target_lufs (default: 1 LU)
`idempotency_key`	No	Optional 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.
`project_item_id`	No	Project item whose local media path should be resolved through Premiere. Provide this or media_path.
`max_true_peak_dbfs`	No	Optional maximum acceptable true peak in dBFS (commonly -1 or -2)
`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_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.2/5.0

Behavior4/5

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

Beyond annotations it discloses the underlying engine (FFmpeg EBU R128), the three metrics emitted, and that no audio is altered and no Premiere state changes. There is a mild tension with readOnlyHint=false, though that is likely a conservative declaration for temp-file writes rather than a claim that the description denies, so it does not rise to a contradiction. It still omits runtime cost for long media and whether temp files are left behind.

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, no filler, with the measurement contract front-loaded and the non-mutation scope immediately after. Every clause carries information an agent needs before calling.

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 no explanation, and the safety profile is covered by annotations. The one genuine gap is that the description claims to read 'a local media file' while the schema also allows resolving media through a Premiere project_item_id, which is meaningful resolution behavior left undocumented.

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 every parameter including the idempotency guard and CEP expectation objects is already documented in the schema. The description adds no parameter-level guidance such as when to prefer project_item_id over media_path, so baseline 3 applies.

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?

Names a specific verb and resource plus the exact measurements produced: 'Measure integrated loudness (LUFS), loudness range (LU), and true peak (dBFS)' via 'FFmpeg's EBU R128 filter'. The second sentence explicitly separates it from the sibling normalize_loudness_file by stating it only analyzes and does not normalize or touch 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?

The clause 'Analysis only: it does not normalize audio or change Premiere' gives a clear positive/negative usage boundary that routes measurement work here and normalization work elsewhere. It stops short of naming the alternative tool explicitly, so the agent must infer the sibling, but the intent is unambiguous.

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

Deploy Server