After Effects MCP Server

by SUBSAHARXN

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

center-layers

Align one, selected, or all layers to the center of an After Effects composition for precise, repeatable placement.

Instructions

Center one layer, selected layers, or all layers in a composition.

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": {
      "compIndex": "<compIndex>"
    },
    "name": "center-layers"
  }
}

Input Schema

Name	Required	Description
`allLayers`	No	Center all layers in the composition.
`compIndex`	Yes	1-based composition index.
`layerName`	No	Target layer name when centering a single layer.
`layerIndex`	No	Target layer index when centering a single layer.
`selectedOnly`	No	Center only selected layers in the composition.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 17, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the action without mentioning side effects, such as modifying layer position values, whether the operation is reversible, or how nesting/anchors are handled. For a mutation tool, this is a notable gap.

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?

A single, front-loaded sentence with zero redundancy. Every word contributes to conveying the tool's purpose, achieving high efficiency.

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?

The tool has 5 parameters, but the description omits how they interact (e.g., whether allLayers overrides other selectors, or if selectedOnly is ignored when layerName is set). Given no output schema or annotations, this missing behavioral context is a significant gap for correct invocation.

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%, so parameters are already well-documented. The description adds no extra semantics beyond echoing selectors like 'selected layers' and 'all layers'. It does not clarify precedence or combinations, but baseline 3 is appropriate since schema handles explanations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb ('Center') and resource ('one layer, selected layers, or all layers in a composition'), distinguishing it from all sibling tools. It immediately communicates the tool's core functionality without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies clear usage contexts: centering individual layers, selected layers, or all layers. While it doesn't explicitly mention alternatives or when-not-to-use, there are no close sibling tools for centering, so the scope is evident and consumers can infer appropriate scenarios.

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