Skip to main content
Glama
Sign In
AE MCP Bridge

AE MCP Bridge

by justajazz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ae_capture_frame

Render one frame of an After Effects composition to PNG for visual inspection. Optionally set time, background, comparison reference, or save path; project unchanged.

Instructions

Render one frame of a composition to PNG and return it as an image for visual inspection. Transparent areas are filled with the composition background color by default. Changes nothing.

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_capture_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
compNoComposition name or numeric item id. Omit to use the active composition.
pathNoOptional absolute PNG path to keep the file (saved as rendered). By default a temporary file is used and deleted.
timeNoTime in seconds. Omit to use the composition's current time.
backgroundNo'comp' (default: composition background color), 'transparent', or a color '#RRGGBB' / [r,g,b].
compareWithNoOptional absolute path to a reference image (PNG/JPEG/WebP/GIF), returned next to the frame for comparison.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the default background-fill behavior for transparent areas and asserts non-destructiveness ('Changes nothing'). It stops short of return-format or auth/permission context, but covers the key behavioral traits for a capture tool.

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?

Three tight sentences, front-loaded with the core action and ending with a one-line safety assertion. Every sentence earns its place with zero filler.

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?

No output schema exists, but the description states it returns an image, and all five params are schema-documented, so an agent has enough to call it. Minor gap: no explicit note on the compareWith side-by-side return or file persistence beyond what the schema says.

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 all five parameters are already documented, making 3 the baseline. The description echoes the background default but adds no syntax or format detail beyond the schema.

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?

States a specific verb+resource (render one frame of a composition) plus the output form (PNG returned as an image). The singular 'one frame' implicitly distinguishes it from the plural sibling ae_capture_frames, letting an agent choose without opening a schema.

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

Usage Guidelines3/5

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

Gives a purpose ('for visual inspection') that implies when to use it, but never names the obvious alternative ae_capture_frames or states when-not to use this single-frame variant. Usage 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.

Deploy Server

Other Tools