premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Set Clip Volume

set_clip_volume

Adjusts an audio clip's Volume > Level in dB (0 unity, negative quieter, positive louder) without changing Essential Sound Amplify automation.

Instructions

Set an audio clip's Volume > Level in dB. Does not read or change Essential Sound Amplify automation.

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": {
      "node_id": "<node_id>",
      "volume_db": "<volume_db>"
    },
    "name": "set_clip_volume"
  }
}

Input Schema

Name	Required	Description
`node_id`	Yes	Node ID of the audio clip
`volume_db`	Yes	Volume in dB (0 = unity, negative = quieter, positive = louder)
`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.
`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

A3.5/5.0

Behavior3/5

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

Annotations already declare a non-destructive, non-read-only, non-idempotent mutation, so the description's main added value is the boundary that Essential Sound Amplify automation is neither read nor modified. It says nothing about undo semantics, whether a saved project is required, or the pre-mutation identity guards, all of which matter for a write tool.

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?

Two sentences, zero filler, with the action stated first and the scope exclusion second. "Volume > Level" is slightly host-jargon-heavy without context, but it is precise and front-loaded.

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 and parameter semantics are fully covered by the schema, so the description only needs to establish intent and scope, which it does. The remaining gap is behavioral: no statement about undo, persistence, or the CEP guard's requirement for a saved project.

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 five parameters, including the nested expected_cep_target guard and idempotency_key, are already documented in the schema. The description's "Level in dB" phrasing merely restates volume_db's own description and adds no new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Set an audio clip's Volume > Level in dB" names a specific verb, resource, and the exact host property being written, which separates it from siblings like set_clip_pan or get_clip_volume. It stops short of naming a sibling alternative, but the scope is unambiguous.

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 second sentence carves out a negative scope (Essential Sound Amplify automation is untouched), which implicitly tells the agent when this tool is the wrong lever. There is no positive when-to-use guidance, no prerequisite (e.g. saved project, sequence open), and no pointer to set_clips_volume for multi-clip edits.

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

Deploy Server