Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.layer.create

Create a solid, shape, text, camera, light, null, or audio layer inside an After Effects composition by name or ID to build scenes, add elements, and automate layer setup.

Instructions

Create a layer in a composition (solid, shape, camera, light, null).

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.create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
typeNosolid
colorNo
widthNo
heightNo
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 disclosure burden for a mutating tool. It does not say that a target composition must be identified, whether compositionId or compositionName is the operative reference (0 required parameters), what defaults are applied, or what happens if neither is supplied — all of which an agent needs before calling a create operation.

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 short sentence with the verb and resource front-loaded and no wasted wording. It is tight, though part of that brevity comes from omitting information rather than from disciplined editing.

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 7-parameter creation tool with no annotations, no output schema, and no schema descriptions, a one-line description is far too thin. Nothing indicates the return value, the required composition reference, or the practical constraints on width/height and color.

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 7 parameters, so the description must compensate and does not. Its only parameter-adjacent content repeats the type enum already present in the schema, leaving name, color, width/height units, and the compositionId vs compositionName relationship entirely unexplained.

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?

States a specific verb and resource ("Create a layer in a composition") and enumerates the layer kinds the tool can produce, which is enough to separate it from ae.layer.delete, ae.layer.duplicate, and ae.layer.transform. The parenthetical is slightly inconsistent with the schema's type enum, which also allows "text" and "audio" but omits those from the description.

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 and no alternatives named. An agent is left to guess whether text layers should go through ae.text.create or whether audio layers come from ae.audio.add instead of this tool, and nothing says a composition must exist first.

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