Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.text.update

Update the text content of an existing After Effects text layer by name or index within a composition, enabling AI-driven text edits in MCP workflows.

Instructions

Update the text content of an existing text layer.

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

Input Schema

NameRequiredDescriptionDefault
textYes
layerNameNo
layerIndexNo
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden and does not meet it. It never says whether the supplied text replaces the entire content or is appended, whether existing character/paragraph styling is preserved, or what happens if the target layer is not a text layer.

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?

A single short sentence with no filler, but the brevity reflects under-specification rather than disciplined editing. The action is front-loaded, which is the one structural strength.

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 five-parameter mutation tool with no annotations and no output schema, one sentence is far short of what an agent needs. The unresolved ambiguity in layer targeting and the unknown behavior on styling makes incorrect invocation likely.

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% across five parameters, so the description must compensate and does not. It says nothing about the four layer-targeting parameters (layerName, layerIndex, compositionId, compositionName) — including which takes precedence when both a name and an index are given — leaving the core identification mechanism undocumented.

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 plus target ("Update the text content of an existing text layer"), which distinguishes it from ae.text.create (new layer) and ae.text.style (formatting rather than content). It does not name those siblings explicitly, so the differentiation is inferential rather than stated.

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?

The only usage signal is the word "existing," implying the layer must already exist. There is no guidance on when to choose this over ae.text.style or ae.text.create, and no prerequisites or failure conditions are mentioned.

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