Sets or changes the volume gain, in decibels, of a selected audio clip on the Premiere Pro timeline. Use it to raise or lower clip audio for balanced mixes.
Adjusts the volume (gain) of an audio clip on the timeline.
| Name | Required | Description | Default |
|---|---|---|---|
| level | Yes | The new audio level in decibels (dB). Can be positive or negative. | |
| clipId | Yes | The ID of the audio clip to adjust |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden for behavioral disclosure. It merely states 'adjusts volume', implying a mutation, but does not reveal whether the change is absolute or relative, whether it affects only selected clips or all, or any side effects such as clipping or undo behavior. Critical details are missing for a modifying operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no redundant wording. It is front-loaded and directly conveys the core action and target, achieving maximum conciseness without lexical waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (2 parameters, no output schema), the description is minimal but incomplete in context. It fails to address usage guidance or behavioral nuances, especially since sibling tools like 'set_clip_volume' exist that could cause confusion. The schema covers parameters, but the description does not provide enough context to fully differentiate the tool or anticipate edge cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers both parameters (clipId and level) with descriptions, achieving 100% coverage. The tool description adds no additional meaning beyond the schema; it does not explain the level values, units (though the schema mentions dB), or relationships between parameters. Baseline 3 is appropriate since the schema already documents the parameters adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool adjusts audio clip volume/gain on the timeline, which is specific and includes the resource. However, it does not explicitly differentiate itself from the sibling tool 'set_clip_volume', which appears to serve a similar purpose, limiting its clarity in distinguishing among alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'set_clip_volume' or 'add_audio_keyframes'. The description lacks any context about suitable scenarios, prerequisites, or conflict with other audio adjustment tools, leaving the agent without direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.