Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.audio.add

Adds an audio track from a footage item to an After Effects composition at a specified start time, enabling synchronized sound in animation and video projects.

Instructions

Add an audio track footage item to a composition.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ae.audio.add"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdNo
filePathNo
startTimeNo
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure and delivers almost none. It does not say whether the operation mutates the composition destructively, whether an existing composition must be open, what happens on duplicate audio adds, or what a successful add returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the action front-loaded and no filler, which is structurally clean. However, the brevity is achieved through omission rather than efficiency; nothing beyond the action is stated.

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

Completeness1/5

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

For a 5-parameter tool with zero schema description coverage, no annotations, and no output schema, the description supplies none of the missing information. An agent cannot determine which identifier parameter to supply or what the call will do to the composition.

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 5 parameters, and the description explains none of them. It gives no hint about the relationship between assetId and filePath (alternatives?) or between compositionId and compositionName, nor about startTime units. 'Audio' and 'composition' in the sentence loosely map to two parameters, but that is all.

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?

Specific verb (Add) plus resource (audio track footage item) plus destination (a composition), which is enough to distinguish it from sibling setters like ae.audio.volume.set and ae.audio.fade.create. It does not clarify what an 'audio track footage item' is or how it relates to asset import, but the core action is unambiguous.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives or conditions under which this should be preferred over importing an asset first. The agent learns what the tool does but nothing about when invoking it is appropriate.

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