Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.composition.update

Update existing After Effects composition settings—dimensions, frame rate, duration, and name—to match new project requirements.

Instructions

Update existing composition settings (dimensions, frame rate, duration).

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.composition.update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
widthNo
heightNo
newNameNo
durationNo
frameRateNo
compositionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 behavioral burden. It says this updates existing settings, but does not disclose whether omitted fields are preserved or reset, whether changes are reversible, what permissions are needed, or how the affected composition is identified.

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?

The description is a single front-loaded sentence with no wasted wording and immediately communicates the mutation scope. It is efficient, though its brevity contributes to the missing operational detail.

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?

This is a mutation tool with seven parameters, no required parameters, no annotations, and no output schema, yet the description leaves key questions unresolved. It does not explain target identification, partial update semantics, required inputs, or return behavior, which is insufficient for a tool of this complexity.

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 seven parameters, so the description must compensate. It names dimensions, frame rate, and duration, but does not map these to width/height/frameRate/duration, does not explain the name versus newName distinction, and does not clarify the role of compositionId or the expected units for frameRate and duration.

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 states a specific verb and resource: update an existing composition's settings, with examples including dimensions, frame rate, and duration. This distinguishes it reasonably well from create/delete/inspect siblings, though it does not spell out how the composition is targeted.

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 explicit guidance on when to use this tool versus alternatives such as ae.composition.create or ae.composition.inspect. It also does not state prerequisites like needing an existing compositionId or whether partial updates preserve unspecified settings.

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