Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.animation.keyframe.update

Update the time or value of an existing After Effects keyframe to adjust animation timing or property values without recreating the keyframe.

Instructions

Update time or value of an existing keyframe.

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": {
      "property": "<property>",
      "keyframeIndex": "<keyframeIndex>"
    },
    "name": "ae.animation.keyframe.update"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNo
valueNo
propertyYes
layerNameNo
layerIndexNo
compositionIdNo
keyframeIndexYes
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?

No annotations are provided, so the description carries the full behavioral burden. It identifies this as a mutation but does not disclose permissions, whether updates are partial, what happens if identifiers are invalid, reversibility, or return behavior.

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 and free of filler. Its terseness is efficient, though not structured to address the multi-parameter targeting needed by this tool.

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 an eight-parameter mutation tool with no annotations, no output schema, and zero schema descriptions, the definition is too sparse. It does not explain target identification, required parameters, or update semantics sufficiently for confident invocation.

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?

Schema description coverage is 0% across eight parameters, so the description must compensate. It mentions only time and value, leaving required identifiers such as property and keyframeIndex and the composition/layer targeting parameters unexplained beyond their names.

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 and resource: update an existing keyframe's time or value. It is clear enough to distinguish from keyframe creation, though it does not explicitly name create as the alternative or clarify how it differs from easing.set.

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?

There is no explicit when-to-use guidance, no mention of prerequisites such as selecting a composition/layer/property, and no exclusions or alternatives. The phrase 'existing keyframe' only weakly implies this is not for creating keyframes.

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