After Effects MCP Server

by SUBSAHARXN

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

search-presets

Find After Effects .ffx presets by name or path. Recursively search directories and return matching preset files.

Instructions

Search After Effects .ffx presets by name or path.

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": {
      "query": "<query>"
    },
    "name": "search-presets"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Search text to match in preset filename or full path.
`maxDepth`	No	Maximum directory depth when recursive is true (default: 10).
`recursive`	No	Recursively search subdirectories (default: true).
`maxResults`	No	Maximum number of preset files to return (default: 200).
`presetRoots`	No	Optional absolute directories to search. Defaults to common Adobe preset locations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 17, 2026

TDQS

B3.4/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 full burden for disclosing behavior. It only states it 'searches' and does not mention return format, recursion or depth defaults, limitations, or that it reads from common Adobe preset locations. This is minimal beyond the obvious read-only nature of 'search'.

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 sentence, uses no filler, and is front-loaded with the key action and resource. It earns its place with zero wasted words.

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?

Despite having 5 parameters and no output schema or annotations, the description does not mention return format or typical use context. It only states the basic purpose, leaving the agent to infer behavior from the schema. The tool is relatively simple but should have disclosed more about results.

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?

Schema description coverage is 100%, so each parameter already has a clear description. The tool description adds no additional parameter meaning, but this is acceptable per the baseline rule for high schema coverage.

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?

Clearly states what the tool does: searches After Effects .ffx presets by name or path. Provides a specific verb ('Search') and resource ('.ffx presets'), distinguishing from siblings like list-presets or apply-preset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when one needs to find a preset by searching for a name or path, but it does not explicitly contrast with sibling tools like list-presets or provide exclusions. No clear 'when-not-to-use' guidance beyond the inherent verb.

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