Skip to main content
Glama

Preview frame

ae_render_frame
DestructiveIdempotent

Renders a frame from an After Effects composition as an image so you can visually verify edits, with zoom, layer isolation, transparency, and difference comparison options.

Instructions

Render a frame of a composition and return it as an image, so you can SEE the result. Inspection options: zoom into a region, render only some layers, show transparency on a checkerboard or a color, and compare against another time or comp as a difference image (black = identical). Large frames are downscaled to maxSize. Use it after visual edits; for motion use ae_render_contact_sheet, for exact colors ae_sample_pixels (via ae_call). Renders through a temporary comp, removed afterwards (hidden layers put back); writes a file only with outputPath, never replacing one unless overwrite.

Input Schema

NameRequiredDescriptionDefault
compNoComposition: item id (number) or exact name. Omit (or "active") for the active/open composition.
timeNoTime in seconds (default: the comp's current time).
layersNoRender only these layers (others are hidden for the render and restored).
regionNoZoom into [x, y, width, height] in comp pixels (scaled up to maxSize, at most 8x).
maxSizeNoLongest side in pixels of the returned image (default 1280).
overwriteNoReplace an existing file at outputPath (default false: refuse).
backgroundNo"checkerboard" to show transparency, or a color like "#808080" behind the comp.
outputPathNoOptional absolute path to also save the PNG to.
compareWithNoDifference image against another time and/or comp (black where identical).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, it discloses important behavior: rendering goes through a temporary comp that is removed afterward, hidden layers are restored, large frames are downscaled, and files are written only with outputPath and never replaced unless overwrite is set. These details substantially clarify side effects and lifecycle.

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 dense but well structured: purpose first, then inspection options, downscaling, alternatives, and side effects. Every sentence carries operational value, and no space is wasted on restating schema details.

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

Completeness5/5

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

Given nine parameters, a nested compareWith object, destructive file-write potential, and no output schema, the description covers what the tool returns and the important behavioral caveats. An agent has enough information to invoke it correctly and understand its side effects.

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

Parameters4/5

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

Schema coverage is 100%, so parameter documentation is already strong. The description adds useful semantic context for key options: region zooming, layer-only rendering, checkerboard/color transparency, difference-image comparison with black meaning identical, and overwrite refusal behavior.

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 verb and resource: render a frame of a composition and return it as an image. It explicitly distinguishes itself from ae_render_contact_sheet for motion and ae_sample_pixels for exact colors, so an agent can select it without inspecting sibling schemas.

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 provides explicit usage guidance: use after visual edits, use ae_render_contact_sheet for motion, and use ae_sample_pixels via ae_call for exact colors. The alternatives and selection conditions are named directly.

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