Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Adjust Audio Levels

adjust_audio_levels

Adjust a clip's audio level in dB by setting its volume to a specific decibel value, providing direct control over loudness.

Instructions

Adjust a clip's Volume > Level in dB. Does not read or change Essential Sound Amplify automation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the audio or video clip
level_dbYesAudio level in dB (0 = unity, negative = quieter, positive = louder)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.4
    • 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"
+}
  2. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=false (a write) and destructiveHint=false (non-destructive), so the safety profile is covered. The description adds useful scoping context by confirming it targets only the Level property and does not read or modify Amplify automation. It does not disclose clamping behavior, keyframe interaction, or whether the value takes effect immediately, but for a simple setter this is adequate.

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 short sentences with zero filler. The primary action ('Adjust a clip's Volume > Level in dB') is front-loaded, and the exclusion sentence earns its place by preventing a common misuse. Nothing could be removed without losing information.

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 simple two-parameter setter with a fully documented schema, an existing output schema, and annotations covering the write profile, the description covers the essentials: what is set, in what unit, and what is deliberately out of scope. The only notable gap is the missing routing guidance relative to set_clip_volume, which an agent might reasonably confuse with this tool.

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 documented as 'Node ID of the audio or video clip' and level_db is documented with units and direction ('0 = unity, negative = quieter, positive = louder'). The description's mention of 'in dB' only restates what the schema already provides. Per the high-coverage baseline, 3 is appropriate.

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?

The description states a specific verb ('Adjust'), a precise resource ('a clip's Volume > Level'), and the unit ('in dB'), making the operation unambiguous. The second sentence clarifies what it does not touch (Essential Sound Amplify automation), which narrows scope further. However, it does not explicitly differentiate itself from the sibling tools set_clip_volume and set_clips_volume, which appear to overlap in function.

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 Essential Sound Amplify exclusion implies a boundary: use this for the clip's Volume > Level property, not for Amplify automation. But no alternative tool is named, and the description gives no explicit 'use X when...' guidance for the closely related volume siblings (set_clip_volume, set_clips_volume). Usage context is implied rather than stated.

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

Deploy Server

Other Tools