Renders one frame of an After Effects composition to PNG and returns it as an image, so you can verify the current visual result before continuing.
After Effects: render one frame of the comp to PNG (default current time) and return it as an image so you can check your work.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | output .png (default: temp file) | |
| time | No | ||
| compositionName | No | Comp name; omit to use the active comp. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the bar is lower, and the description does add real context: the return payload is an image and the capture defaults to the current time. However, it does not disclose that a file is written to disk (temp file by default) or whether the PNG reflects pre/post-effect state — behaviorally relevant given the readOnly claim.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with verb, output artifact, default behavior and rationale. Nothing is wasted and nothing important is buried.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the return format (image) so no output schema is needed, and it names the defaults for zero-argument calls. For a render/export operation it is still thin: no word on output resolution, whether the temp PNG persists, or how it interacts with an unsaved project state.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67%, so the schema already documents path (default temp file) and compositionName (omit for active comp). The description only reinforces the time default and adds nothing about format, resolution, or what `time` is measured in — the one parameter with no schema description at all.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource — render one frame of the comp to PNG — plus a concrete motivation (check your work). It is clearly distinct from mutation tools like ae_addEffect, but it never names its closest alternatives (pr_exportFrame, xapp_preview, ae_getCompState) so the agent must infer host-specific routing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"so you can check your work" implies a verification/preview use case, and the parenthetical "(default current time)" tells the agent it can be called with zero arguments. There is no explicit when-not and no mention of the sibling preview/export tools, so the choice between this and ae_renderQueue or pr_exportFrame is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.