Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.layer.inspect

Retrieves detailed properties, transform coordinates, and timing for a specified After Effects layer so you can verify or debug composition setup before editing.

Instructions

Inspect detailed layer properties, transform coordinates, and timing.

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.layer.inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNameNo
layerIndexNo
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It implies a read-only inspection but does not explicitly confirm that nothing is mutated, describe permission requirements, explain missing-layer behavior, or disclose return structure beyond three broad categories.

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?

The definition is a single front-loaded sentence with no padding or repetition. However, its brevity leaves important details unstated, so its concision is efficient but underspecified.

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 tool with four undocumented optional parameters, no annotations, and no output schema, the description is too thin. It does not explain parameter use, identifier resolution, expected return values, or error behavior, leaving key details needed to invoke it correctly unspecified.

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

Parameters1/5

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

The tool has four parameters with 0% schema description coverage, and the description provides no meaning for layerName, layerIndex, compositionId, or compositionName. It also does not clarify whether one identifier is preferred or how the optional composition identifiers interact with the layer identifiers.

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 specific verb ('Inspect') and resource ('layer'), and names concrete data it returns: detailed properties, transform coordinates, and timing. It is clear what the tool does, though it does not distinguish itself from the sibling ae.layer.transform or explain whether transform data is returned versus modified.

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 explicit when-to-use guidance, no mention of alternatives such as ae.layer.transform, and no stated prerequisites or exclusions. Usage is only implied by the word 'Inspect'.

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