Skip to main content
Glama
Sign In
mcp-ae

mcp-ae

by shibin0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ae_get_composition_layers

Retrieve all layers in an After Effects composition by providing its name. Use this to inspect the layer hierarchy before making changes.

Instructions

Get all layers in a specific After Effects composition

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": {
      "comp_name": "<comp_name>"
    },
    "name": "ae_get_composition_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
comp_nameYesThe name of the composition

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. 'Get' accurately signals a read-only listing and there is nothing misleading, but the description does not disclose potential behavioral details such as error behavior when comp_name does not exist, ordering of layers, or whether the composition must be currently open.

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?

The description is a single, front-loaded sentence with no filler or redundant information. Every word earns its place.

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

Completeness3/5

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

The tool is simple, with one fully documented parameter, and the description states the core action. However, with no output schema and no annotations, the description does not clarify the return shape (e.g., layer names vs. full layer objects) or error conditions, leaving those details to runtime discovery.

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?

The input schema already fully documents comp_name (coverage 100%), so the baseline for this dimension is 3. The description adds no parameter-specific meaning beyond restating that a specific composition is targeted, which is acceptable but not enhancing.

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 uses a clear verb and resource: 'Get all layers in a specific After Effects composition.' It is unambiguous about the operation, but it does not explicitly distinguish itself from closely related siblings like ae_get_layer_properties, 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 Guidelines3/5

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

The intended use is implied: when an agent needs to retrieve all layers for a named composition. However, there is no explicit when-to-use guidance or mention of alternatives, so an agent is left to infer when ae_get_composition_layers should be preferred over ae_get_layer_properties or other layer tools.

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