Skip to main content
Glama
Sign In
After Effects MCP Server

After Effects MCP Server

by ionutsss1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

mcp_aftereffects_applyEffectTemplate

Apply predefined effect templates to After Effects layers by composition and layer index. Use optional custom settings to override defaults.

Instructions

Apply a predefined effect template to a layer in After Effects

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": {
      "compIndex": "<compIndex>",
      "layerIndex": "<layerIndex>",
      "templateName": "<templateName>"
    },
    "name": "mcp_aftereffects_applyEffectTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
compIndexYes1-based index of the target composition in the project panel.
layerIndexYes1-based index of the target layer within the composition.
templateNameYesName of the effect template to apply.
customSettingsNoOptional custom settings to override defaults.

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 for behavioral disclosure. It only states the action without revealing important traits such as whether existing effects are replaced, whether the layer must be selected, or whether the operation is destructive. This is insufficient for a tool that applies changes to a layer.

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, clear sentence with no redundant words. It is appropriately sized and front-loaded with the verb and object, making it easy to parse.

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 no output schema and no annotations, the description should provide more context about what happens after applying the template, whether any output (e.g., success/failure) is returned, and how customSettings interact with the template. The current one-sentence description leaves critical operational details unspecified, especially for a tool with a nested object parameter.

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?

All four parameters are fully described in the input schema (100% coverage), so the baseline is 3. The description itself adds no additional meaning beyond the schema, such as explaining the customSettings object structure or how template defaults work, but the schema already provides adequate semantics.

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 ('apply') and resource ('predefined effect template to a layer in After Effects'), making the core function understandable. However, it does not differentiate this from closely related sibling tools such as 'apply-effect' or 'apply-effect-template', leaving some ambiguity about which tool to choose.

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 like 'apply-effect' or 'apply-preset'. It does not mention any exclusions, prerequisites, or typical scenarios, leaving the agent without clear selection criteria.

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