Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.animation.easing.set

Set keyframe interpolation, temporal easing, and speed/influence values to control animation timing in After Effects.

Instructions

Configure keyframe interpolation, temporal easing, and speed/influence.

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.easing.set"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyYes
layerNameNo
layerIndexNo
easeInSpeedNo
easeOutSpeedNo
compositionIdNo
keyframeIndexYes
compositionNameNo
easeInInfluenceNo
easeOutInfluenceNo
interpolationTypeNobezier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 full burden. It implies a mutation ('Configure') but does not disclose permissions, reversibility, error conditions, or what happens if the keyframe does not exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise and front-loaded with the purpose, but it is too sparse for an 11-parameter mutation tool and lacks structure to guide invocation.

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

Completeness1/5

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

Given 11 parameters, no annotations, no output schema, and a mutation operation, the description is critically incomplete. It omits parameter guidance and behavioral details needed to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 11 parameters and 0% schema description coverage, the description must explain parameter meanings. It does not mention any parameter names, types, ranges, or defaults, leaving all parameter semantics undocumented.

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 (Configure) and resource (keyframe interpolation, temporal easing, speed/influence), making the operation clear. It does not explicitly differentiate from siblings like keyframe.update, but the focus on easing is distinct enough.

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 guidance on when to use this tool versus alternatives such as ae.animation.keyframe.update or keyframe.create. The description gives no context, prerequisites, or exclusions.

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