Skip to main content
Glama
TheLlamainator

After Effects MCP Server

set-effect-property

Set or keyframe any property on an existing layer effect in After Effects by specifying its name, index, or path. Assign values, add keyframes, apply expressions, and control easing.

Instructions

Set or keyframe any property on an existing layer effect using name/index/path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compIndexYes1-based index of the target composition in the project panel.
layerIndexYes1-based index of the target layer within the composition.
effectIndexNo1-based index of the effect in the layer's Effects group.
effectNameNoDisplay name of the effect to target.
effectMatchNameNoInternal matchName of the effect to target.
propertyPathNoPath from effect root to target property, e.g. ['Compositing Options', 'Effect Opacity'] or [3, 1].
propertyNameNoFallback target property name or matchName.
propertyIndexNoFallback target property index under the effect root.
keyframeIndexNoOptional keyframe index to edit graph/value directly without resolving by time.
valueNoValue to assign to the target property.
timeInSecondsNoIf provided, sets a keyframe at this time using value.
expressionStringNoOptional expression string to set on the target property.
keyframeOptionsNoOptional graph/easing controls applied to the keyframe at timeInSeconds.
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as overwriting behavior, error handling, or side effects. The brief description lacks necessary context for a complex tool.

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 description is a single sentence, highly concise. However, for a tool with 13 parameters, it could be slightly more structured or detailed without being verbose.

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?

Given the complexity (13 parameters, nested objects, keyframe options) and no output schema, the description is too brief. It omits important context about targeting logic, prerequisites, and behavior.

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 100%, so each parameter already has a description. The overall description says 'using name/index/path' but adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 the action (set or keyframe), target (any property on an existing layer effect), and method (using name/index/path). It distinguishes from sibling tools like 'add-any-effect' and 'remove-effect'.

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?

No guidance on when to use this tool vs alternatives like 'set-effect-keyframe' or 'setLayerKeyframe'. No mention of prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TheLlamainator/after-effects-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server