Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.text.create

Creates a new text layer in an After Effects composition with configurable font, size, color, alignment, and position.

Instructions

Create a new text layer in a composition with font, size, color, and alignment.

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

Input Schema

NameRequiredDescriptionDefault
fontNo
nameNo
textYes
colorNo
fontSizeNo
positionNo
alignmentNocenter
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it: nothing is said about whether creating a layer mutates the active composition, whether the operation is reversible, what defaults apply when font/color/size are omitted, or what is returned. For a creation tool this is a meaningful gap.

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 front-loaded sentence with no filler; it leads with the verb and resource. It is efficient, though its brevity is partly the source of the specification gaps rather than a virtue in itself.

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?

For a 9-parameter creation tool with no annotations and no output schema, the definition is under-specified: target selection, position semantics, default behavior, and return value are all unaddressed. It is adequate only at the minimum-viable level.

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 9 parameters, yet the description only mentions font, size, color, and alignment — and 'size' does not match the schema's fontSize naming. Critical ambiguities remain unexplained, notably compositionId vs compositionName (are both required? does one take precedence?) and the units/coordinate space for position.

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 states a specific verb and resource ('Create a new text layer in a composition') and enumerates the main attributes (font, size, color, alignment), which is enough to distinguish it from ae.text.style and ae.text.update. It stops short of naming those siblings, so it is clear but not fully differentiated.

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 prerequisites (e.g., whether a composition must already exist or be active), and no routing to alternatives such as ae.text.style for restyling an existing layer or ae.text.update for edits. Usage must be inferred from the name and the word 'new'.

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