Premiere Pro MCP Server

Get Clip Volume

get_clip_volume

Read-onlyIdempotent

Read an audio clip's volume level in dB to verify the actual value applied, since setValue can clamp silently. Use this to confirm the level after adjustment.

Instructions

Read an audio clip's Volume > Level in dB. Use this to verify a level actually applied - setValue() clamps silently. Does not report Essential Sound Amplify automation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`node_id`	Yes	Node ID of the audio clip

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds value beyond annotations by explaining that setValue() clamps silently, positioning this read as the authoritative verification path, and by disclosing the Amplify automation limitation. No contradiction with annotations.

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?

Three short sentences, each earning its place: purpose, use-case rationale, and limitation. The purpose is front-loaded in the first sentence, and there is zero filler or repetition of information already present in the annotations or schema.

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?

For a single-parameter read tool with full schema coverage, an output schema, and readOnly/idempotent annotations, the description covers the purpose, the verification use case, and a key limitation. Minor edge cases — such as return behavior when no volume is set — are left to the output schema, which is an acceptable division of labor.

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% — node_id is already documented as 'Node ID of the audio clip.' The description's phrase 'audio clip's' reinforces the parameter's target type but adds no syntax, format, or edge-case meaning beyond the schema. Baseline 3 is appropriate since the schema fully carries the parameter documentation burden.

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?

The description states a specific verb and resource: 'Read an audio clip's Volume > Level in dB.' This precisely identifies the operation, the target property path, and the unit of measurement, clearly distinguishing it from write tools like set_clip_volume and broad reads like get_clip_properties. The final sentence further defines scope by naming what is excluded (Essential Sound Amplify automation).

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 description gives a concrete when-to-use: 'Use this to verify a level actually applied - setValue() clamps silently,' which tells the agent this is the verification read after a set operation. It also notes a limitation of the tool ('Does not report Essential Sound Amplify automation'). However, it never names alternative tools or explicit when-not conditions, leaving some sibling routing 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