Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

setup_ducking

Builds an audio ducking curve with keyframes for pre-fade, duck-in, duck-out, and post-fade transitions, lowering music or SFX around speech or effects.

Instructions

High-level wrapper around add_audio_keyframes that builds a ducking curve from a base level + ducking windows. Computes 4 keyframes per window (pre-fade, duck-in, duck-out, post-fade) plus boundary keyframes at clip start/end. Replaces the manual "8 keyframes per video" pattern from Sprint 3. Times are clip-source-time absolute (same convention as add_audio_keyframes).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clipId": "<clipId>",
      "baseDb": "<baseDb>",
      "duckingWindows": "<duckingWindows>"
    },
    "name": "setup_ducking"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseDbYesSustained level in dB (e.g. -25 for music bed under voice)
clipIdYesThe ID of the music/SFX clip to apply ducking to
clipEndTimeNoClip end time anchor for last keyframe; if omitted, last duck window endTime + 1s is used
fadeSecondsNoRamp time for each transition (default 0.2s = 6 frames @30fps)
clipStartTimeNoClip start time anchor for first keyframe (default 0)
duckingWindowsYesWindows where the clip should duck below baseDb. Empty array = sustained baseDb only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose side effects. It mentions building a curve and computing keyframes, which implies modifying the clip's audio keyframes, but it does not explicitly state that the tool will add or modify keyframes on the clip, nor does it mention any potential destructive actions, permissions, or other behavioral impacts.

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 two concise sentences that efficiently convey the tool's purpose, behavior, and key timing convention. It avoids unnecessary detail and is well-structured for quick understanding.

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?

The description explains the core functionality and input interpretation well, but it does not mention what the tool returns or any error conditions (e.g., what happens if duckingWindows are invalid). Since there is no output schema, a brief note on return behavior would improve completeness, but the current description covers essential usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 6 parameters are fully described in the schema (100% coverage), and the description adds crucial context such as times being clip-source-time absolute and the meaning of empty duckingWindows. The parameter meanings are clear and unambiguous.

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 clearly states what the tool does: it builds a ducking curve by wrapping add_audio_keyframes, specifying the inputs (base level + ducking windows) and the output (keyframes). It also distinguishes itself from the manual '8 keyframes per video' pattern, making its purpose unambiguous.

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 indicates it is a high-level wrapper for add_audio_keyframes and replaces a manual pattern, giving some context on when to use it. However, it does not explicitly state when to use this instead of directly using add_audio_keyframes or other alternatives, nor does it mention any exclusions or conditions.

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