Premiere Pro MCP Server

Add Audio Keyframes

add_audio_keyframes

Add audio level keyframes to a clip to create fades or volume changes. Specify times and dB levels for precise audio control.

Instructions

Add audio level keyframes to create fades or level changes

Input Schema

TableJSON Schema

Name	Required	Description	Default
`node_id`	Yes	Node ID of the clip
`keyframes`	Yes	Array of keyframe objects with time_seconds and level_db

Output Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.19.0Oct 3, 2026
- changedInput schema / properties / keyframes / items / properties / level_db / description
```
Previous value: -"Audio level in dB"New value: +"Audio level in dB (maximum +15 dB)"
```
- addedInput schema / properties / keyframes / items / properties / level_db / maximum
```
Added value: +15
```
- addedInput schema / properties / keyframes / items / properties / time_seconds / minimum
```
Added value: +0
```
- addedInput schema / properties / keyframes / minItems
```
Added value: +1
```

Changed2 schema fields changedv1.18.6Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / properties / data / description

Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."

Changed1 schema field changedv1.14.9Sep 8, 2026
- removedInput schema / properties / keyframes / items / additionalProperties
```
Removed value: -{}
```

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"
+}

Changed2 schema fields changedv1.4.0Jul 27, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / keyframes / items

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "level_db": {
+      "description": "Audio level in dB",
+      "type": "number"
+    },
+    "time_seconds": {
+      "description": "Time in seconds relative to clip start",
+      "type": "number"
+    }
+  },
+  "required": [
+    "time_seconds",
+    "level_db"
+  ],
+  "type": "object"
+}

First observedv1.1.1May 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare the safety profile (non-destructive, non-idempotent, closed-world), so the description need not restate it. It adds nothing behavioral, though – it does not say whether existing keyframes are merged, replaced, or appended, which is material for a mutation on a clip's audio automation.

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?

A single front-loaded sentence with no wasted words. It is efficient, though arguably terse given the operation modifies clip automation.

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?

With a rich input schema, an output schema, and annotations covering the safety profile, the definition is largely sufficient for correct invocation. The remaining gap is what happens to pre-existing keyframes, which is minor against the structured data already present.

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 the schema fully documents node_id, time_seconds, and level_db (including the +15 dB cap). The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 (add) and resource (audio level keyframes) plus the outcome (fades or level changes). It distinguishes the audio-specific nature from the generic add_keyframe sibling, though it never names a sibling explicitly.

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?

Usage is implied by the stated goal ("to create fades or level changes"), which tells the agent roughly when this applies. However, no alternatives are offered – it does not contrast with adjust_audio_levels, set_clip_volume, or the generic add_keyframe, so the agent must infer which to pick.

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

Deploy Server