Skip to main content
Glama
Sign In
After Effects MCP

After Effects MCP

by leo10m2010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Render After Effects composition

after_effects_render
Destructive

Render a saved After Effects project through aerender, specifying a composition or using the render queue to generate output files.

Instructions

Render a saved After Effects project through aerender. Specify a composition or omit it to render queued items. This writes output files and may run for a long time.

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": {
      "project_path": "<project_path>"
    },
    "name": "after_effects_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
soundNo
end_frameNo
compositionNoExact composition name. Omit to use the project's render queue.
output_pathNoAbsolute output path. Image sequences may use a [#####] token.
start_frameNo
project_pathYesAbsolute path to a saved project.
frame_incrementNo
timeout_secondsNo
output_module_templateNo
reuse_running_instanceNo
render_settings_templateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations: it states the tool is destructive (writes files) and long-running. Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description reinforces and adds performance expectations. No contradictions.

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 very concise: three sentences, each serving a purpose. The first states the main action, the second clarifies composition usage, and the third notes side effects and runtime. No unnecessary words.

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 (11 parameters, no output schema, destructive), the description is incomplete. It lacks details on most parameters, return values, success criteria, and prerequisites. The agent would need to infer how to set up the render correctly from minimal information.

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 only 27%, and the description provides minimal parameter details. It mentions the 'composition' parameter (specify or omit) and implies 'project_path' is required, but fails to explain other key parameters like sound, start_frame, end_frame, output_path, timeout, etc. The description does not compensate for the low schema coverage.

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 clearly states the tool's purpose: 'Render a saved After Effects project through aerender.' It specifies the resource (saved project), verb (render), and method (aerender). The mention of specifying a composition or omitting it distinguishes this tool from sibling tools, which cover other After Effects operations like adding solids or opening projects.

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 gives guidance on when to use the tool: to render a saved project. It explains the two modes (specify composition or use render queue) and notes that it writes output files and may run for a long time, implying it's for final output. It does not explicitly exclude alternatives, but since no other render tool exists among siblings, the context is sufficient.

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

Deploy Server

Other Tools