Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.composition.create

Create a new After Effects composition by specifying dimensions, frame rate, and duration to set up your animation or video project.

Instructions

Create a new composition with width, height, frame rate, and duration.

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": {
      "name": "<name>"
    },
    "name": "ae.composition.create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
widthNo
heightNo
durationNo
frameRateNo
pixelAspectNo

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 behavioral burden and it does not pay it. It never says whether the new composition becomes active in the project, what happens on a duplicate name, what is returned (an ID? an object?), or what permissions/state are required for this mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tightly front-loaded sentence with no filler, which is good, but for a six-parameter creation tool the terseness shades into under-specification rather than economy.

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?

A creation tool with six parameters, no annotations, and no output schema needs more than a single sentence. Missing: the required `name` parameter, `pixelAspect`, units for duration/frameRate, and the post-creation behavior (does the new comp open or become active?). Only the schema's defaults partially cover the gap.

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%, so the schema supplies only types, defaults, and positivity constraints — not meaning. The description names width, height, frame rate, and duration but omits `name` (the only required parameter) and `pixelAspect` entirely, and gives no units for duration or frameRate.

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 gives a specific verb and resource ("Create a new composition") plus the four main settings, which reads clearly against siblings like ae.composition.update, ae.composition.delete, and ae.composition.inspect. It stops short of an explicit differentiation statement, but the operation is unambiguous.

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 guidance on when to create a new composition versus updating or inspecting an existing one, no prerequisite context (e.g. must a project be open?), and no named alternative. Usage is only inferable from the verb.

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