Skip to main content
Glama

film_ui

Capture a motion filmstrip of a UI by driving interaction steps, then composing frames into a captioned strip image with real motion enabled.

Instructions

Render a filmstrip: drive optional interaction steps (applied first, so a click can trigger the transition to watch), then capture frames with real motion turned on — every other tool stays reduced-motion for deterministic pixels; this is the one place the point is watching motion play — and compose them into one captioned strip image. Returns the actual frame count/interval/scale used (each is clamped to a documented ceiling, so a hostile request degrades instead of hanging) plus the strip's pixel dimensions, a downscaled inline preview, and a resource_link to the full-resolution strip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNo
scaleNoPer-cell strip scale, `0.05..=1.0` (clamped; non-finite clamps to 1.0).
stepsNoAn array of interaction steps, applied before capture starts (optional — e.g. `[{"click":{"role":"button","name":"Add"}}]`).
themeNo
framesNoFrames to capture (clamped to a documented ceiling).
descriptionYesThe UI description: a `fenestra/1` JSON object.
interval_msNoMilliseconds between captured frames (clamped to a documented ceiling).
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it drives interaction steps first, captures frames with real motion, clamps parameters with documented ceilings to prevent hanging, and returns specific values (frame count, interval, scale, pixel dimensions, preview, resource link). This provides comprehensive transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph that front-loads the main purpose. It is informative but somewhat run-on. It could be broken into shorter sentences for better readability, but it earns its sentences without unnecessary fluff.

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?

Given the tool's complexity (7 params, no output schema), the description covers the main workflow, safety mechanisms, and return values. However, it could be more explicit about the output structure, especially since there is no output schema to fall back on. It provides a good overview.

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 71%, so the baseline is 3. The description adds context about how steps are applied and clamping, but does not add new details for the undocumented parameters (size, theme) or significantly enhance understanding of those documented. It provides process context rather than per-parameter semantics.

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 clearly states the tool's purpose: 'Render a filmstrip' with a specific verb and resource. It distinguishes itself from sibling tools by explicitly noting that 'every other tool stays reduced-motion for deterministic pixels; this is the one place the point is watching motion play', making it unique among rendering 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?

The description provides guidance on when to use this tool: for capturing motion with real motion enabled, as opposed to other reduced-motion tools. It also explains the optional interaction steps and clamping behavior, but could more explicitly list alternative tools and when not to use it.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/richer-richard/fenestra'

If you have feedback or need assistance with the MCP directory API, please join our Discord server