Skip to main content
Glama
Sign In
AE MCP Server

AE MCP Server

by p10q
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

copy_keyframes

Copy keyframes between properties in Adobe After Effects to transfer animation data between layers or properties.

Instructions

Copy keyframes from one property to another

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>",
      "sourceLayer": "<sourceLayer>",
      "sourceProperty": "<sourceProperty>",
      "targetLayer": "<targetLayer>",
      "targetProperty": "<targetProperty>"
    },
    "name": "copy_keyframes"
  }
}

Input Schema

NameRequiredDescriptionDefault
compIdYesID of the composition
sourceLayerYesSource layer index
sourcePropertyYesSource property path
targetLayerYesTarget layer index
targetPropertyYesTarget property path
timeOffsetNoTime offset in seconds
reverseKeyframesNoReverse the keyframe order

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'copy' implies a non-destructive read-then-write operation, the description doesn't address critical behavioral aspects: whether this overwrites existing keyframes in the target property, what permissions are required, whether it works across different property types, or what happens on failure. This leaves significant gaps 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, efficient sentence that states exactly what the tool does with zero wasted words. It's appropriately sized for a tool with well-documented parameters in the schema.

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 a mutation tool with 7 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, what happens on success/failure, whether it validates property compatibility, or any error conditions. The combination of mutation behavior and missing structured documentation requires more descriptive content.

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 100%, so all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond implying a source-to-target copying operation. This meets the baseline expectation when the schema does the heavy lifting, but doesn't provide extra value like explaining property path format or layer indexing conventions.

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 action ('copy') and resources ('keyframes from one property to another'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'offset_keyframes' or 'reverse_keyframes' that also manipulate keyframes, which prevents a perfect score.

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 sibling tools like 'offset_keyframes', 'reverse_keyframes', and 'batch_keyframes' available, there's no indication of when copying keyframes is appropriate versus other keyframe manipulation operations.

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