Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.composition.inspect

Inspect an After Effects composition's properties and list its layers to confirm structure and layer setup before editing or rendering.

Instructions

Inspect composition properties and list its layers.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
compositionIdNo

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 supplied, so the description carries the full burden. "Inspect" implies a read, but it never confirms read-only behavior, whether it errors on a missing composition, whether layer listing is paginated or truncated, or how large a composition is handled — all material for a tool that is the entry point to a layer tree.

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 tight sentence with the verb front-loaded and no filler. It is efficient, but the brevity is partly under-specification rather than pure concision.

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?

With two undocumented parameters, no annotations, and no output schema, the description should explain the identifier choice and sketch the return shape (properties plus a layer list). Neither is present, leaving the agent guessing about which identifier to pass and what comes back.

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?

Schema description coverage is 0% for both parameters, and the description adds nothing: it does not say whether "name" and "compositionId" are alternatives, whether one takes precedence, or what format either expects. Both are optional in the schema yet neither is explained.

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 ("Inspect") plus resource ("composition properties") and a secondary effect ("list its layers"). Clearly distinct from the create/delete/update siblings, though it doesn't clarify the boundary with ae.layer.inspect, which also surfaces layer data.

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 guidance on when to use this versus ae.composition.update or ae.layer.inspect, and no prerequisites stated. The reader must infer that this is the read path for a composition, and nothing explains which of the two parameters to supply.

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