Skip to main content
Glama
TheLlamainator

After Effects MCP Server

mcp_aftereffects_applyEffect

Applies a specified effect to a layer in an After Effects composition, supporting effect name or matchName with optional parameters.

Instructions

Apply an effect to a layer in After Effects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compIndexYes1-based index of the target composition in the project panel.
layerIndexYes1-based index of the target layer within the composition.
effectNoGeneric effect identifier. Can be either exact display name or matchName.
effectIdentifierNoAlias for effect. Can be either exact display name or matchName.
effectNameNoDisplay name of the effect to apply (e.g., 'Gaussian Blur').
effectMatchNameNoAfter Effects internal name for the effect (more reliable, e.g., 'ADBE Gaussian Blur 2').
effectSettingsNoOptional parameters for the effect (e.g., { 'Blurriness': 25 }).
Behavior2/5

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

No annotations are present, so the description bears full responsibility for disclosure. It states only the action without detailing effects on existing properties, whether the operation is destructive, permission requirements, or what happens upon success/failure. This is insufficient 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.

Conciseness3/5

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

The description is a single sentence, making it concise, but it is too minimal for a tool with 7 parameters and many siblings. It could be restructured to front-load purpose and include brief usage context without adding bulk. A score of 3 reflects acceptable conciseness with room for improvement.

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?

Given the tool's complexity (7 parameters, nested objects, no output schema), the description is severely lacking. It does not explain return values, side effects, order of operations, or error conditions. The agent lacks critical context to use the tool effectively.

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 the baseline is 3. The tool description adds no extra meaning beyond the parameter descriptions already present in the schema, hence a score of 3.

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?

The description clearly states the verb (apply) and resource (effect to a layer in After Effects). However, it does not differentiate from many sibling tools like 'add-any-effect', 'apply-effect', or 'apply-effect-template', which have similar functions. A score of 4 reflects clarity without sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'apply-effect' or 'add-any-effect'. There is no mention of prerequisites, typical use cases, or explicit exclusions, leaving the agent without contextual decision-making support.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TheLlamainator/after-effects-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server