Premiere Pro MCP Server

Set Clips Volume

set_clips_volume

Sets volume in decibels on every audio clip in a track, or only chosen clip indices, in one round trip instead of one call per clip.

Instructions

Set the volume (in dB) on every audio clip of a track, or on a list of clip indices. One round trip instead of one call per clip - essential for sequences with dozens of clips.

Input Schema

TableJSON Schema

Name	Required	Description
`volume_db`	Yes	Volume in dB applied to every selected clip (0 = unity, max +15)
`track_index`	Yes	Audio track index (0-based)
`clip_indices`	No	Optional clip indices on that track. Omit to apply to all clips.

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.11.3Aug 19, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The annotations already indicate the operation is non-readonly and non-destructive. The description adds the useful batch/round-trip efficiency context, but it does not disclose potential side effects like overwriting existing volume settings or behavior on invalid clip indices. It is adequate but not rich.

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, front-loaded with the core operation and target, followed by the most important usage rationale. No filler or redundancy; every sentence earns its place.

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 batch setter with fully documented parameters, an output schema, and a clear use case, the description provides enough context for an agent to invoke it correctly. No critical behavioral or scoping information is missing.

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 coverage is 100%, and each parameter already has a meaningful description. The tool description reinforces the track/clip-index semantics but adds no new format, constraints, or edge-case information beyond what the schema provides.

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 the exact operation ('Set the volume in dB'), the target resource ('every audio clip of a track'), and the optional scoping ('or on a list of clip indices'). This clearly differentiates it from the singular sibling set_clip_volume by emphasizing the bulk/multi-clip behavior.

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?

Explicitly gives the key use case: 'One round trip instead of one call per clip - essential for sequences with dozens of clips.' This tells the agent when the bulk behavior is valuable, though it does not explicitly name the alternative for a single-clip operation.

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

Deploy Server