Skip to main content
Glama
Sign In
AE MCP Bridge

AE MCP Bridge

by justajazz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ae_get_audio_info

Retrieve audio details for an After Effects layer, such as source file path, audio levels, keyframes, and markers, without modifying the project.

Instructions

Audio info of a layer: source file path, audio levels and their keyframes, existing markers. Changes nothing.

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": {
      "layer": "<layer>"
    },
    "name": "ae_get_audio_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
compNoComposition name or numeric item id. Omit to use the active composition.
layerYesLayer name or 1-based index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the read-only nature ('Changes nothing') and what the response contains, which is genuinely useful. It omits edge behavior such as what happens when the layer has no audio or how comp/layer name resolution failures surface.

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?

A single front-loaded sentence that opens with the resource and then lists the returned fields, ending with the safety claim. No filler, nothing to trim.

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?

There is no output schema, but the description stands in for one by naming the returned data (path, levels with keyframes, markers). The main gap is that it doesn't distinguish this metadata read from ae_analyze_audio's likely waveform analysis.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (comp, layer) are already fully documented in the schema, including the omit-to-use-active-comp default and 1-based indexing. The description adds nothing beyond that, so the baseline 3 applies.

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?

It names a specific verb and resource ('Audio info of a layer') and enumerates exactly what that info contains: source file path, audio levels with keyframes, and existing markers. That enumeration separates it cleanly from siblings like ae_set_audio_levels, ae_analyze_audio, and ae_add_markers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Changes nothing' implies a safe read-only inspection, so the context is inferable, but the description never states when to reach for this tool versus ae_analyze_audio or ae_get_layer_timing, nor any prerequisites. Usage is implied rather than guided.

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