Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.layer.duplicate

Duplicate an existing layer in a specified composition by name or index to reuse layer content and settings without rebuilding it.

Instructions

Duplicate an existing layer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ae.layer.duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNameNo
layerIndexNo
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full disclosure burden for a mutating operation. It does not say where the copy is placed, whether the name is auto-suffixed, whether the original is modified, or what identity the new layer receives.

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 front-loaded and free of waste, but it is undersized rather than concise — there is no second sentence earning its place by resolving the target-selection and return-value questions.

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 zero annotations, no output schema, and four undescribed parameters, the definition is far too thin. An agent cannot reliably determine how to address the layer or what the duplication produces.

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 four parameters, and the description adds almost nothing: "an existing layer" hints that one must identify a target but gives no meaning for layerName versus layerIndex, nor explains why compositionId and compositionName both exist. The schema fields are essentially 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 pairs a specific verb ("Duplicate") with a specific resource ("an existing layer"), so an agent can tell it apart from destructive siblings like ae.layer.delete. It stops short of naming how duplication differs from ae.layer.create, so it is clear but not sibling-differentiated.

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 duplicate versus create a layer from scratch, nor any prerequisite such as which composition or layer must be targeted. The agent is left to infer the workflow entirely.

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