Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.effects.apply

Apply an effect to a layer by match name or display name, targeting a specific composition and layer for precise automation.

Instructions

Apply an effect by match name or display name to a layer.

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": {
      "effectName": "<effectName>"
    },
    "name": "ae.effects.apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNameNo
effectNameYes
layerIndexNo
displayNameNo
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 the full behavioral burden. It implies a mutation ('Apply') but does not state whether it adds a new effect instance, requires an existing effect, needs specific permissions, or what the result looks like.

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

Conciseness4/5

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

The single sentence is short and front-loads the operation and target. It is efficiently worded, though its brevity contributes to the missing parameter and behavioral detail rather than being a structural flaw.

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?

This is a mutation tool with six parameters, no annotations, and no output schema, so the description needs to carry substantial context. It identifies the basic action but leaves parameter relationships, naming behavior, and side effects undocumented.

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?

With six parameters and 0% schema description coverage, the description must compensate but only references effect matching by name/display name and the target layer. It does not clarify the roles of layerName vs. layerIndex or compositionId vs. compositionName, nor which parameters are required or optional.

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 uses a specific verb and resource ('Apply an effect') and names the target ('to a layer'), so the operation is identifiable. It does not explicitly distinguish this from the sibling 'ae.effects.configure', but the core purpose is clear.

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 'ae.effects.configure' or when not to use it. The mention of 'match name or display name' hints at naming options but does not explain prerequisites or selection criteria.

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