Skip to main content
Glama
higgsfield-ai

fnf-local-pluging-bridge-mcp

by higgsfield-ai
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

Render frame

ae_render_frame

Render a single After Effects frame to PNG to visually verify edits, with deterministic headless capture and viewer-accurate color handling.

Instructions

Render a single frame to PNG. Use to visually verify edits. The agent's 'eyes' — pair with mutations for a visual feedback loop. Headless and deterministic. In color-managed projects (workingSpace != None) the capture applies AE's own display transform via a transient OCIO Display Transform adjustment layer, and the PNG comes back viewer-accurate and sRGB-tagged. Where that layer cannot be used — read-only mode, an AE without the OCIO effect, or a failed capture calibration — the result falls back to a pure-math ACES conversion or to raw values with an explicit colorWarning; check colorPipeline / colorWarning on the response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeYesTime in seconds to render.
outPathYesAbsolute path to write the PNG. Parent directory is created if missing.
colorManagedNo'auto' (default): detect the working space and return a viewer-accurate, 8-bit sRGB-tagged PNG. 'off': raw legacy output (16-bit, untagged, working-space values — dark/wrong-looking in color-managed projects).
compNameOrIdYesComposition name or numeric item id.
useDisplayStartTimeNoIf true, `time` is interpreted relative to comp.displayStartTime. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the single destructiveHint annotation, the description discloses headless and deterministic execution, the transient OCIO color transform behavior, fallback paths, and the colorWarning/colorPipeline response fields to inspect. This is substantial behavioral transparency.

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 front-loaded with purpose and usage, then provides necessary technical caveats about color management. Every sentence earns its place; there is no filler or empty marketing language.

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?

For a tool with no output schema and sparse annotations, this description is unusually complete. It explains the output format, color-managed behavior, fallback scenarios, and which response fields to check, while parameters are already fully documented in the schema.

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% with detailed parameter documentation. The description reinforces color behavior but does not add meaningful parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 single frame to PNG.' It goes further by framing the tool as the agent's 'eyes' for visually verifying edits, which clearly differentiates it from the sibling project-management and automation tools.

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?

It explicitly says to use the tool to visually verify edits and recommends pairing it with mutations for a visual feedback loop. It does not name exclusions or alternative tools, but the intended usage context is unambiguous.

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

Install Server

Other Tools