After Effects MCP Server

by SUBSAHARXN

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

apply-preset

Apply an After Effects .ffx preset file to a target layer by providing composition index, layer index, and preset path.

Instructions

Apply an After Effects .ffx preset file 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": {
      "compIndex": "<compIndex>",
      "layerIndex": "<layerIndex>",
      "presetPath": "<presetPath>"
    },
    "name": "apply-preset"
  }
}

Input Schema

Name	Required	Description
`compIndex`	Yes	1-based index of the target composition in the project panel.
`layerIndex`	Yes	1-based index of the target layer within the composition.
`presetPath`	Yes	Absolute path to the .ffx preset file.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 17, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action but does not explain whether the preset replaces existing effects, what compatibility requirements exist, or what the result/consequences are on the layer. This is a significant gap for a mutation tool.

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, focused sentence that conveys the core action without unnecessary words. It is front-loaded with the verb and resource, making it instantly understandable.

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?

The tool is a simple mutation, but the description lacks critical behavioral context (e.g., side effects, prerequisites) and there is no output schema to describe return values. With no annotations, the description should be more comprehensive to be complete for an agent.

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 has 100% description coverage for all three parameters (compIndex, layerIndex, presetPath). The description adds no extra meaning beyond the schema, so the baseline of 3 is appropriate.

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 specific action: applying an After Effects .ffx preset file to a layer. It distinguishes itself from sibling tools like apply-effect (which likely applies effects by name) by specifying the preset file format.

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 given on when to use this tool versus alternatives like apply-effect, apply-effect-template, or other preset-related tools. The description implies usage (applying a preset) but does not provide context, prerequisites, or exclusions.

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