Skip to main content
Glama

setLayerKeyframe

Set keyframes for specific layer properties in After Effects compositions at precise times using AI-driven automation. Define composition, layer, property, time, and value for accurate animation control.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
valueNoThe value for the keyframe (e.g., [x,y] for Position, [w,h] for Scale, angle for Rotation, percentage for Opacity)

Implementation Reference

  • src/index.ts:489-524 (registration)
    MCP tool registration for 'setLayerKeyframe', including description, input schema (layer/comp indices, property name, time, value), and handler that queues the command via writeCommandFile.
    server.tool(
      "setLayerKeyframe", // Corresponds to the function name in ExtendScript
      "Set a keyframe for a specific layer property at a given time.",
      {
        ...LayerIdentifierSchema, // Reuse common identifiers
        propertyName: z.string().describe("Name of the property to keyframe (e.g., 'Position', 'Scale', 'Rotation', 'Opacity')."),
        timeInSeconds: z.number().describe("The time (in seconds) for the keyframe."),
        value: KeyframeValueSchema
      },
      async (parameters) => {
        try {
          // Queue the command for After Effects
          writeCommandFile("setLayerKeyframe", parameters);
          
          return {
            content: [
              {
                type: "text",
                text: `Command to set keyframe for "${parameters.propertyName}" on layer ${parameters.layerIndex} in comp ${parameters.compIndex} has been queued.\n` +
                      `Use the "get-results" tool after a few seconds to check for confirmation.`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error queuing setLayerKeyframe command: ${String(error)}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • The handler function for the setLayerKeyframe tool. It writes the command and parameters to a temporary file ('ae_command.json') for the After Effects MCP Bridge Auto panel to detect and execute the corresponding ExtendScript.
    async (parameters) => {
      try {
        // Queue the command for After Effects
        writeCommandFile("setLayerKeyframe", parameters);
        
        return {
          content: [
            {
              type: "text",
              text: `Command to set keyframe for "${parameters.propertyName}" on layer ${parameters.layerIndex} in comp ${parameters.compIndex} has been queued.\n` +
                    `Use the "get-results" tool after a few seconds to check for confirmation.`
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error queuing setLayerKeyframe command: ${String(error)}`
            }
          ],
          isError: true
        };
      }
    }
  • Shared Zod schema for identifying target composition and layer by 1-based indices, reused in setLayerKeyframe and other layer tools.
    const LayerIdentifierSchema = {
      compIndex: z.number().int().positive().describe("1-based index of the target composition in the project panel."),
      layerIndex: z.number().int().positive().describe("1-based index of the target layer within the composition.")
    };
  • Zod schema for the keyframe value input, using z.any() for flexibility across different property types.
    const KeyframeValueSchema = z.any().describe("The value for the keyframe (e.g., [x,y] for Position, [w,h] for Scale, angle for Rotation, percentage for Opacity)");
  • Core helper function used by all command-queuing tools, including setLayerKeyframe, to write the command name and parameters to ae_command.json in TEMP dir for polling by After Effects bridge.
    function writeCommandFile(command: string, args: Record<string, any> = {}): void {
      try {
        const commandFile = path.join(process.env.TEMP || process.env.TMP || '', 'ae_command.json');
        const commandData = {
          command,
          args,
          timestamp: new Date().toISOString(),
          status: "pending"  // pending, running, completed, error
        };
        fs.writeFileSync(commandFile, JSON.stringify(commandData, null, 2));
        console.error(`Command "${command}" written to ${commandFile}`);
      } catch (error) {
        console.error("Error writing command file:", error);
      }
    }
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 burden of behavioral disclosure. It states the tool 'Set a keyframe,' implying a write operation that modifies the project, but fails to disclose critical behavioral traits such as permission requirements, whether the operation is reversible, or potential side effects like overwriting existing keyframes. This gap is significant for a mutation tool with zero annotation coverage.

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 front-loads the core action ('Set a keyframe') and specifies the target without any wasted words. It is appropriately sized for the tool's complexity, making it easy for an agent to parse quickly.

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 tool's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It lacks information about behavioral traits, usage context, and return values, which are crucial for an agent to invoke the tool correctly. The high schema coverage helps with parameters, but overall, the description does not provide enough contextual information for safe and 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?

The schema description coverage is 100%, meaning all parameters are well-documented in the input schema. The description adds no additional meaning beyond what the schema provides, such as explaining parameter interactions or constraints. However, since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description does not compensate for any gaps but also does not detract from the existing documentation.

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 ('Set a keyframe') and specifies the target ('for a specific layer property at a given time'), which is a specific verb+resource combination. However, it does not explicitly differentiate from sibling tools like 'setLayerExpression' or 'test-animation', which might involve similar layer operations, leaving some ambiguity about when to choose this tool over alternatives.

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. It lacks context about prerequisites, such as needing an existing composition or layer, and does not mention sibling tools like 'setLayerExpression' for expression-based animations or 'test-animation' for broader animation tasks. This omission leaves the agent without clear usage instructions.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dakkshin/after-effects-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server