AE MCP Bridge

by justajazz

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

ae_list_available_effects

Search installed After Effects effects by display name, matchName, or category without modifying the project.

Instructions

Search effects installed in After Effects by display name, matchName or category. Changes nothing.

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": "ae_list_available_effects"
  }
}

Input Schema

Name	Required	Description
`max`	No	Default 200.
`query`	No
`includeObsolete`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 17, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the important behavioral fact that the operation is side-effect free ('Changes nothing.'), which is genuinely useful. However it says nothing about result volume, pagination, or ordering despite a 'max' cap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler. The search facets and the safety note are packed efficiently, though the second sentence is terse to the point of being cryptic.

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?

For a no-annotation, no-output-schema search tool with an undocumented parameter, the description is adequate but thin. It does not address return shape or the 'includeObsolete' semantics, leaving meaningful gaps an agent would need to guess at.

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 coverage is only 33% (only 'max' is documented). The description compensates partially by explaining what 'query' matches against (display name, matchName, category), but 'includeObsolete' is left entirely unexplained in both schema and description.

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?

States a specific verb+resource (search effects installed in After Effects) and enumerates the searchable facets (display name, matchName, category). It implicitly contrasts with ae_list_layer_effects by scoping to 'installed' effects, but does not name that sibling explicitly.

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 when-to-use guidance, no prerequisites, and no routing to alternatives. An agent must infer on its own whether this is the right tool versus ae_list_layer_effects or ae_apply_effect. The 'Changes nothing.' clause is a safety note, not usage guidance.

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