After Effects MCP Server

Overview Schema Source Related Servers Discussions Admin

list-presets

Find available After Effects .ffx presets in common Adobe folders or custom directories. Control recursive search, folder depth, and result limits to match your preset scan.

Instructions

List available After Effects .ffx presets from common or provided folders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-presets"
  }
}

Input Schema

Name	Required	Description
`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: 500).
`presetRoots`	No	Optional absolute directories to search for presets. Defaults to common Adobe preset locations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 17, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It implies a read-only operation ('List available') and specifies the source folders, but it does not state what the tool returns (e.g., file paths vs. names), whether it requires After Effects to be running, or any limits like recursion defaults. This is adequate for a simple list tool but lacks depth.

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, containing only 10 words, and is front-loaded with the core action ('List available After Effects .ffx presets'). Every word is purposeful and there is no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but there is no output schema, so the description should clarify what the tool returns. It does not. Additionally, with sibling search-presets present, the description could have mentioned how list-presets differs (e.g., 'lists all presets from folders, while search-presets filters by query'). Overall, it provides the basic purpose but leaves these contextual gaps.

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 schema provides 100% description coverage for all four parameters, so the baseline is 3. The tool description adds minimal semantic value beyond the schema; 'common or provided folders' merely paraphrases the schema's presetRoots description, and no details about maxDepth, recursive, or maxResults are included in the 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 uses a specific verb ('List'), identifies the resource ('After Effects .ffx presets'), and specifies the scope ('from common or provided folders'). This clearly distinguishes it from sibling tools like apply-preset and search-presets by focusing on enumeration from filesystem locations.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (when you need to discover available presets from common or custom folders), but it does not explicitly mention alternatives or when not to use it. Since sibling search-presets exists, a brief note on how it differs would have made this a 5.

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