Skip to main content
Glama

smart_export

Convert recorded .webm files to GIF or MP4 with tooltip overlays showing magnified interaction details, keeping the full viewport visible for product demos.

Instructions

Convert a recorded .webm to GIF or MP4 with tooltip overlays on interactions.

The full viewport stays visible. When an interaction happens (click, type, hover), a clean tooltip inset appears showing a magnified close-up of that area with a small arrow pointing toward the interaction. Modern, minimal design (Linear/Figma style).

The tooltip positions itself on the opposite side of the screen from the interaction.

Perfect for product demos where viewers need to see both the full UI context AND the detail.

Example workflow:

  1. record_page → interact_page (clicks, typing, etc.) → stop_recording

  2. smart_export with the webmPath and timelinePath from stop_recording

  3. Get a polished GIF/MP4 with tooltip overlays on every interaction

Compare with cinematic_export which crops the entire frame to follow the action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpsNoFrame rate for GIF output
widthNoOutput width for GIF (height auto-scaled)
formatNoOutput format (default: gif)gif
webmPathYesPath to the .webm file from stop_recording
tooltipSizeNoSize of the tooltip inset in pixels (default 380)
magnifyScaleNoHow much to magnify inside the tooltip (default 1.6x)
timelinePathYesPath to the -timeline.json file from stop_recording
holdPerTargetNoHow long to show each tooltip (seconds)
Behavior4/5

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

With no annotations, the description fully explains the tool's behavior: it adds tooltip overlays on interactions, positions them opposite the interaction, and produces a polished output. However, it does not mention side effects like file creation or deletion.

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 well-structured with a front-loaded overview, bullet points, and an example workflow. It is slightly verbose but each sentence adds value.

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 8 parameters and no output schema, the description provides sufficient detail about the tool's purpose and behavior. The example workflow and comparison with siblings enhance completeness.

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 coverage is 100%, so baseline is 3. The description adds context for tooltipSize, magnifyScale, and holdPerTarget, but does not significantly enhance the meaning beyond the schema descriptions.

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 converts .webm to GIF/MP4 with tooltip overlays, distinguishing it from cinematic_export which crops the frame. The verb 'convert' and resource 'recorded .webm' are specific, and the comparative mention differentiates siblings.

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 an example workflow and compares with cinematic_export, making it clear when to use this tool. It does not explicitly state when not to use, but the context is sufficient for an agent to decide.

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/mcpware/pagecast'

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