Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.audio.volume.set

Set audio level in decibels for a specific layer by name or index, so you can adjust or mute clip loudness in a composition.

Instructions

Set audio level in decibels for an audio layer.

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": {
      "volumeDb": "<volumeDb>"
    },
    "name": "ae.audio.volume.set"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNo
volumeDbYes
layerNameNo
layerIndexNo
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: it doesn't say whether the value overwrites or multiplies existing level, whether the setting is keyframable/animatable, or whether an animation must already exist. Nothing about permissions, undo, or what happens when the target layer is not an audio layer.

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 short sentence with the action and unit front-loaded and no filler. Efficiency is good, but the terseness crosses into under-specification for a six-parameter tool.

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

Completeness2/5

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

With six parameters, zero schema coverage, no annotations, and no output schema, the definition should explain layer targeting, composition scoping, and the time parameter. It explains none of these, leaving the agent to guess at how to address a layer and what 'time' means.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, and the description only clarifies the unit for volumeDb and that a layer is the target. It says nothing about how layerName, layerIndex, compositionId, and compositionName interact or which takes precedence, and nothing about what the 'time' parameter does or about the -96 to 12 dB bounds.

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?

States a specific verb and resource ('Set audio level') plus the unit ('in decibels') and the target ('for an audio layer'), which separates it from ae.audio.add and ae.audio.fade.create by implication. It never names a sibling explicitly, so it stops short of full differentiation.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to any alternative such as the fade or add tools. The agent must infer the entire usage context from the name alone.

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