Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.audio.fade.create

Creates an audio fade-in or fade-out on a selected audio layer to control volume transitions at a specified start time and duration.

Instructions

Create an audio fade-in or fade-out on 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": {
      "fadeType": "<fadeType>",
      "startTime": "<startTime>",
      "duration": "<duration>"
    },
    "name": "ae.audio.fade.create"
  }
}

Input Schema

NameRequiredDescriptionDefault
durationYes
fadeTypeYes
layerNameNo
startTimeYes
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 are supplied, so the description carries the full burden, and it discloses almost nothing. It doesn't say whether the layer must already be an audio layer, whether an existing fade on the same range is replaced or stacked, whether the operation is undoable, or what units startTime and duration use.

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 efficient sentence with the action front-loaded and no filler. The brevity is clean rather than padded, though it shades into under-specification given the parameter surface.

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?

For a 7-parameter mutation tool with zero annotation coverage, no output schema, and no parameter documentation, one sentence is not enough. An agent can guess the intent but not the call contract.

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 7 parameters, and the description compensates for only a fraction: it implies fadeType ('in' or 'out') and that a layer is targeted. Nothing explains the layerName vs layerIndex vs compositionId vs compositionName resolution rules, nor the units and bounds of startTime and duration.

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 names a specific verb and resource ('Create an audio fade-in or fade-out') plus the target ('on an audio layer'), which is more precise than the bare tool name. It does not distinguish this from adjacent siblings such as ae.audio.volume.set or ae.animation.keyframe.create, so it stops short of a 5.

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 prerequisites, and no mention of alternatives for achieving similar envelope effects. The agent must infer entirely on its own whether to reach for this tool or a keyframe/volume tool.

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