Skip to main content
Glama
Sign In
AE MCP Server

AE MCP Server

by p10q
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_keyframe_advanced

Set keyframes in After Effects with precise control over temporal and spatial interpolation for smooth animations.

Instructions

Set a keyframe with interpolation options

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": {
      "compId": "<compId>",
      "layerIndex": "<layerIndex>",
      "propertyPath": "<propertyPath>",
      "time": "<time>",
      "value": "<value>"
    },
    "name": "set_keyframe_advanced"
  }
}

Input Schema

NameRequiredDescriptionDefault
compIdYesID of the composition
layerIndexYesIndex of the layer
propertyPathYesProperty path (e.g., 'Transform.Position', 'Transform.Scale')
timeYesTime in seconds
valueYesValue for the keyframe (number or array depending on property)
interpolationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 mentions 'interpolation options' but doesn't disclose critical behavioral traits: whether this is a mutation (likely yes, given 'Set'), what permissions are needed, if it overwrites existing keyframes, error conditions, or response format. For a tool with 6 parameters and no annotations, this is a significant gap.

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, efficient sentence with zero waste. It's front-loaded with the core action ('Set a keyframe') and qualifies it directly ('with interpolation options'), making it easy to parse. Every word earns its place.

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 (6 parameters, nested objects, no output schema, no annotations), the description is inadequate. It doesn't explain what a keyframe is in context, how interpolation works, what happens on success/failure, or typical usage patterns. For an 'advanced' tool with rich parameters, more context is needed to guide effective use.

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 description coverage is 83% (high), so the baseline is 3. The description adds minimal value beyond the schema, mentioning 'interpolation options' which aligns with the 'interpolation' parameter but doesn't explain semantics like how interpolation affects animation, when spatial vs. temporal applies, or default behaviors. It doesn't compensate for the 17% coverage gap (e.g., 'value' parameter lacks description in schema).

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 clearly states the verb ('Set') and resource ('a keyframe') with a specific feature ('with interpolation options'), making the purpose understandable. It distinguishes from the simpler 'set_keyframe' sibling tool by mentioning 'advanced' interpolation capabilities, though it doesn't explicitly contrast with other keyframe-related siblings like 'set_keyframe_interpolation_type' or 'set_keyframe_velocity'.

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. With many sibling tools for keyframe manipulation (e.g., 'set_keyframe', 'set_keyframe_interpolation_type', 'set_keyframe_velocity'), there's no indication of when this advanced version is preferred, what prerequisites exist, or typical use cases.

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