After Effects MCP Server

by TheLlamainator

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

remove-effect

Target and remove one effect or all effects from a layer in Adobe After Effects using composition and layer indices.

Instructions

Remove one specific effect (or all effects) from 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": {
      "compIndex": "<compIndex>",
      "layerIndex": "<layerIndex>"
    },
    "name": "remove-effect"
  }
}

Input Schema

Name	Required	Description
`compIndex`	Yes	1-based composition index.
`layerIndex`	Yes	1-based layer index.
`effectIndex`	No	1-based effect index within the layer's Effects group.
`effectName`	No	Display name of the effect to remove.
`effectMatchName`	No	Internal match name of the effect to remove.
`removeAll`	No	If true, remove all effects from the layer.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 17, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description discloses the core behavior but omits any side effects, irreversibility, or error conditions. With no annotations available, the description carries the full burden and does not clarify what happens when removing an effect fails or when removeAll is combined with effectName.

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, brief sentence that immediately states the purpose. It follows a clear structure with no filler.

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 tool with six parameters and no output schema or annotations, the description is too thin. It does not explain how the effect selection parameters (effectIndex, effectName, effectMatchName) interact, nor what happens if none are specified when removeAll is false. This leaves the agent uncertain about invocation requirements.

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 input schema already describes all six parameters with 100% coverage, so the baseline is 3. The description adds only the high-level distinction between removing one effect versus all, which is also captured by the removeAll parameter description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Remove') and the target ('effect' on a 'layer'), and mentions the dual mode (specific or all). This distinguishes it from sibling tools like apply-effect or list-layer-effects.

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?

No guidance is provided on when to use this tool versus alternatives like set-effect-property or list-layer-effects. The description does not mention contexts in which removal is appropriate or if there are prerequisites.

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