Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.effects.configure

Set parameter values on an effect already applied to a layer or composition, letting you adjust effect settings by name or index.

Instructions

Configure parameters and values of an applied effect.

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": {
      "propertyName": "<propertyName>"
    },
    "name": "ae.effects.configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo
layerNameNo
effectNameNo
layerIndexNo
effectIndexNo
propertyNameYes
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/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 the full burden, and it discloses almost nothing beyond the verb. It does not say whether the change is reversible, whether the effect must exist for the call to succeed, what happens to unspecified properties, or what the response contains. "Configure" implies mutation but nothing about its side effects is stated.

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?

A single front-loaded sentence with no filler, so nothing is wasted, but the terseness is under-specification rather than discipline. For an 8-parameter mutation tool there is no structure at all to organize identity, target, and value concerns.

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

Completeness1/5

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

With 8 parameters, 0% schema description coverage, no annotations, and no output schema, the description is the only source of behavioral information and supplies one sentence. An agent cannot determine target resolution rules or mutation semantics from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, and the description compensates only by hinting that "parameters and values" correspond to propertyName and value. It never explains the name-vs-index duplication (compositionId/compositionName, layerName/layerIndex, effectName/effectIndex), which identifier wins if both are supplied, or what type value accepts.

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?

"Configure parameters and values of an applied effect" gives a specific verb and resource, and the word "applied" signals it operates on an effect that already exists, which implicitly separates it from ae.effects.apply. It never names that sibling or any other alternative, so the differentiation is left to inference.

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?

There is no when-to-use guidance, no stated prerequisite that the effect must first be applied, and no mention of what to do instead when adding a new effect. The agent must guess the ordering between ae.effects.apply and this tool.

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