Skip to main content
Glama

ae_setTransform

Set a layer's After Effects transform values—position, scale, rotation, opacity, anchor point, and 3D orientation—or create keyframes when a time is specified.

Instructions

After Effects: set transform — position, scale (number or [x,y]), rotation, opacity, anchorPoint, xRotation, yRotation, orientation. With time, sets keyframes instead.

Input Schema

NameRequiredDescriptionDefault
timeNo
layerYesLayer name or 1-based index.
scaleNo
opacityNo
positionNo
rotationNo
xRotationNo
yRotationNo
anchorPointNo
orientationNo
compositionNameNoComp name; omit to use the active comp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only but non-destructive mutation, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by explaining that providing a time value changes the tool from setting a static transform to setting keyframes.

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?

Two tightly packed sentences with no filler: the property list is front-loaded and the keyframe behavior follows immediately. Every clause contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter mutation tool with low schema description coverage and no output schema, the description is adequate but incomplete. It covers the main transform fields and keyframe behavior, but leaves out compositionName handling, units, layer lookup semantics and expected side effects.

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 coverage is only 18%, so the description must do more work. It enumerates every transform property it accepts and clarifies that scale can be a number or [x,y], but it omits units, ranges, coordinate-space details and does not mention compositionName at all.

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 states a specific verb, resource and property set: set a layer transform in After Effects with position, scale, rotation, opacity, anchorPoint, xRotation, yRotation and orientation. It is clearly distinguishable from generic sibling tools like ae_setProperty and ae_setKeyframe, though it does not explicitly name those alternatives.

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

Usage Guidelines3/5

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

The description gives an important usage rule: with a time value it sets keyframes instead of a static value. However, it does not say when to prefer ae_setKeyframe, ae_setProperty or ae_setKeyframes, and it omits prerequisites such as the need for an active comp or existing layer.

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