Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Add Audio Keyframes

add_audio_keyframes

Apply audio level keyframes to a clip to create fades or volume changes by specifying times and decibel levels.

Instructions

Add audio level keyframes to create fades or level changes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip
keyframesYesArray of keyframe objects with time_seconds and level_db

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. Changed1 schema field changedv1.14.9
    • removedInput schema / properties / keyframes / items / additionalProperties
      Removed value: -{}
  2. 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"
+}
  3. Changed2 schema fields changedv1.4.0
    • 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"
+}
  4. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive or idempotent. The description adds the audio-level domain and fade/level-change intent, but it does not disclose whether existing keyframes are replaced or merged, or whether the array should be sorted by time_seconds.

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?

The description is a single front-loaded sentence with no filler or redundant schema repetition. It conveys the action and purpose immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter mutation with an output schema and fully described parameters, this is minimally adequate. However, it omits practical context such as whether the tool applies only to audio clips, whether it appends or replaces existing keyframes, and which sibling tools are better suited for non-keyframed level adjustments.

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?

The input schema provides full 100% coverage for both parameters: node_id and keyframes with key-level time_seconds and level_db descriptions. The description adds no additional parameter semantics, so the schema carries the burden and 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 uses a specific verb and resource: 'Add audio level keyframes' and explains the intended outcome: 'create fades or level changes.' This is clear and useful, though it does not explicitly distinguish itself from sibling tools like add_keyframe or adjust_audio_levels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a usage scenario ('to create fades or level changes') but offers no explicit when-to-use guidance or alternatives. It does not mention when to prefer adjust_audio_levels or add_keyframe, nor does it state prerequisites such as the clip being an audio clip or having an editable audio track.

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