Skip to main content
Glama
Sign In
AE MCP Server

AE MCP Server

by p10q
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_text_layer_advanced

Create text layers in After Effects with precise control over fonts, colors, spacing, positioning, and advanced typographic features for professional motion graphics.

Instructions

Add a text layer with advanced formatting options

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": {
      "compId": "<compId>",
      "text": "<text>"
    },
    "name": "add_text_layer_advanced"
  }
}

Input Schema

NameRequiredDescriptionDefault
compIdYesID of the composition
textYesText content
nameNoName of the layer
sourceTextNoText document properties
positionNoInitial position [x, y] or [x, y, z]
anchorNoAnchor point [x, y] or [x, y, z]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 fully disclose behavioral traits. It mentions 'advanced formatting options' but fails to specify that this is a creation/mutation tool, what permissions are needed, whether it modifies existing layers, or what happens on success/failure. This leaves critical behavioral aspects unclear for a tool with complex inputs.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. It directly communicates the tool's function, making it easy to parse and understand quickly.

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?

Given the tool's complexity (6 parameters with nested objects, no output schema, and no annotations), the description is insufficient. It doesn't address behavioral aspects like mutation effects, error handling, or output expectations, leaving gaps that could hinder an agent's ability to use the tool effectively in context.

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

Parameters3/5

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

Schema description coverage is 100%, providing detailed parameter documentation. The description adds minimal value by hinting at 'advanced formatting options', which loosely relates to the 'sourceText' object parameters, but doesn't explain specific semantics beyond what the schema already covers. This meets the baseline for high schema coverage.

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 clearly states the action ('Add') and resource ('text layer'), specifying 'advanced formatting options' to differentiate from the simpler sibling tool 'add_text_layer'. However, it doesn't explicitly contrast with other text-related tools like 'modify_text_properties' or 'create_text_on_path', keeping it from a perfect score.

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 is provided on when to use this tool versus alternatives. With sibling tools like 'add_text_layer' (simpler) and 'modify_text_properties' (for existing layers), the description lacks any context about prerequisites, timing, or comparisons, leaving the agent without usage direction.

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

Deploy Server

Other Tools