Skip to main content
Glama
Sign In
After Effects MCP Server

After Effects MCP Server

by ionutsss1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

setLayerKeyframe

Sets a keyframe for a layer property at a specified time in After Effects, enabling precise animation control.

Instructions

Set a keyframe for a specific layer property at a given time.

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>",
      "layerIndex": "<layerIndex>",
      "propertyName": "<propertyName>",
      "timeInSeconds": "<timeInSeconds>"
    },
    "name": "setLayerKeyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNoThe value for the keyframe (e.g., [x,y] for Position, [w,h] for Scale, angle for Rotation, percentage for Opacity)
compIndexYes1-based index of the target composition in the project panel.
layerIndexYes1-based index of the target layer within the composition.
propertyNameYesName of the property to keyframe (e.g., 'Position', 'Scale', 'Rotation', 'Opacity').
timeInSecondsYesThe time (in seconds) for the keyframe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without revealing what happens if the optional 'value' parameter is omitted, whether existing keyframes are overwritten, or what the tool returns. This is a significant gap for a mutation tool.

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?

The description is a single concise sentence that directly states the core action without any filler or redundancy. Every word contributes to understanding.

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 no annotations, no output schema, and an optional 'value' parameter whose behavior is unexplained, the description is not complete enough for an agent to fully understand the tool's behavior. The schema covers parameter names and types, but the description fails to convey key contextual nuances such as keyframe overwriting or the significance of the optional value.

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?

The input schema already provides 100% coverage of parameter descriptions, so the baseline is 3. The description adds little beyond restating 'specific layer property' and 'given time,' and it fails to clarify the optional 'value' parameter, which is not included in the required list. However, since the schema handles most semantics, a 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 uses a specific verb 'Set' with a clear resource: 'a keyframe for a specific layer property at a given time.' It clearly distinguishes from sibling tools like set-effect-keyframe by focusing on layer properties rather than effects.

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?

The description provides no guidance on when to use this tool versus alternatives. There are related sibling tools such as set-effect-keyframe and setLayerExpression, but the description does not mention them or any exclusions, leaving the agent without explicit usage direction.

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