Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.layer.transform

Update an After Effects layer's position, scale, rotation, opacity, and anchor point to adjust placement and visibility in a composition.

Instructions

Update layer transform properties (position, scale, rotation, opacity, anchorPoint).

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.layer.transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo
opacityNo
positionNo
rotationNo
layerNameNo
layerIndexNo
anchorPointNo
compositionIdNo
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?

With no annotations, the description carries the full behavioral burden but only establishes that this is a mutation affecting the listed properties. It does not explain whether omitted properties remain unchanged, whether existing keyframes are overwritten or a static value is set at the current time, or how invalid or ambiguous targets are handled.

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?

The single sentence is front-loaded with the verb and resource, and its property list is compact and non-redundant. It is easy to scan, although its extreme brevity leaves no room for important invocation caveats.

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 nine-parameter mutation with no required parameters, no annotations, no output schema, and no parameter descriptions, one general sentence is insufficient for reliable invocation. Target selection and precedence, empty-call behavior, partial-update semantics, and value conventions all remain unspecified.

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?

The parenthetical list covers five of the nine parameters but largely repeats names already present in the schema. At 0% schema description coverage, it needed to explain array dimensionality and units, rotation and scale conventions, compositionId versus compositionName, and layerName versus layerIndex, but provides none of that semantics or targeting precedence.

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 gives a specific action, resource, and scope: updating a layer's position, scale, rotation, opacity, and anchorPoint. This distinguishes transform editing from general layer creation or inspection, but it does not explicitly differentiate the tool from animation- or keyframe-related siblings.

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?

Changing the listed transform values is the only implied usage context. There is no guidance on prerequisites, when animated changes should use another tool, or how to choose between composition and layer identifiers.

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