Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.text.style

Apply font, size, fill/stroke colors, tracking, and justification to text layers in After Effects to control typography and match a composition's design.

Instructions

Apply typographic styling to text (font, size, fill/stroke colors, tracking, justification).

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.text.style"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNo
fontSizeNo
trackingNo
fillColorNo
layerNameNo
layerIndexNo
strokeColorNo
strokeWidthNo
compositionIdNo
justificationNo
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 provided, so the description carries the full burden of disclosure. It never states that this mutates an existing text layer, whether changes are reversible or undoable, what happens when zero of the 11 optional parameters are supplied, or what the tool returns.

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?

One front-loaded sentence with a parenthetical field list — economical and easy to scan. The brevity is not the problem; the missing content is, so this dimension scores well without being a 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?

Eleven parameters, none required, no annotations, no output schema, and multiple layer/composition targeting options whose resolution order is undocumented. For a styling mutation with this much surface area, the single sentence leaves an agent unable to determine which target will be affected when several targeting fields are supplied.

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 11 parameters, so the description must compensate. It covers only font, size, colors, tracking, and justification, and completely omits the targeting parameters (layerName, layerIndex, compositionId, compositionName) and strokeWidth, which are the ones most likely to be misused.

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 names a specific verb and resource ("Apply typographic styling to text") and enumerates the properties touched, which is well above a tautology. It does not, however, distinguish the tool from the sibling pair ae.text.create / ae.text.update, leaving ambiguous whether this styles existing text or produces it.

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 use this versus ae.text.update or ae.text.create, and no prerequisites such as whether a text layer must already exist. An agent gets no signal about preconditions or ordering.

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