Skip to main content
Glama
23d1

after-effects

by 23d1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Render a composition

ae_render

Render an After Effects composition to a video file by adding it to the render queue and starting the render. Specify an output path, optional time range, and render settings; the tool blocks until rendering finishes.

Instructions

Add a composition to the render queue and render it. After Effects is blocked while this runs, so keep the range short unless you mean it. Use ae_save_frame for quick visual checks instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd time in seconds. Omit for the work area end.
compNoComposition name, project item id, or index. Omit for the active comp.
startNoStart time in seconds. Omit for the work area start.
overwriteNoReplace outputPath if a file is already there. Default: false, which fails with a clear error instead — After Effects would otherwise block on a modal overwrite prompt.
queueOnlyNoAdd to the render queue without starting it, so the user can press Render themselves.
outputPathYesAbsolute output path, e.g. '/Users/me/out.mov'.
outputModuleNoOutput module template name, e.g. 'H.264 - Match Render Settings - 15 Mbps'. Omit for the default.
renderSettingsNoRender settings template name. Default: 'Best Settings'.
timeoutMinutesNoHow long to wait. Default: 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations only mark readOnlyHint=false and openWorldHint=false, so the description adds important behavioral context: 'After Effects is blocked while this runs.' This is a material behavioral trait that an agent needs to know before invoking, and it is not captured by the annotations. It could mention results/failure behavior, but the overwrite modal behavior and timeout are already in the schema.

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 compact: one action sentence, one warning, and one routing alternative. It is front-loaded and every sentence earns its place without filler or repetition.

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

Completeness4/5

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

For a 9-parameter mutation tool with no output schema, the description gives the essential behavioral warning, the action, and the alternative to use instead. All parameters are documented in the schema, so nothing needed to invoke correctly is missing; a small gap is that the return/result behavior is not described, but that is secondary for a render tool.

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 and the description does not need to repeat parameter details. The 'keep the range short' hint relates to start/end but does not add new parameter-level meaning beyond what the schema already documents.

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 states a specific action with a verb and resource: 'Add a composition to the render queue and render it.' It also distinguishes itself from the sibling ae_save_frame by noting that tool is for 'quick visual checks instead,' so an agent can tell which operation to choose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance by warning that After Effects is blocked and advising to keep the range short unless truly intended, and it names an alternative, ae_save_frame, for quick visual checks. This is clear selection guidance beyond the schema.

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