Skip to main content
Glama

mimic_render_url

Render JavaScript-heavy web pages in a headless browser to extract the full DOM. Use when a URL returns a loading shell instead of meaningful HTML. Returns a path to the rendered HTML file for further processing.

Instructions

Render a client-rendered web page in a headless browser and extract the full DOM. Use this when a URL returns only a JS shell, loading spinner, or hydration scaffold — not meaningful HTML. The renderer waits for the page to fully hydrate using generic readiness signals (text density, node count, DOM stability) before extracting. Returns the path to the rendered HTML file which can then be used as build input. On failure, returns a classified error (auth wall, endless loading, empty shell, etc).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to render.
outputNoOptional output file path. Defaults to internal/builds/rendered-{timestamp}.html.
timeoutNoMax render wait in ms. Default: 30000.
cookiesNoAuth cookies for the target domain. Each: { name, value, domain, path }.
Behavior5/5

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

Describes hydration waiting strategy, return value (path to HTML file), and error classification. Adds rich behavioral context beyond annotations, which only provide readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. No contradiction.

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 paragraph of 5 sentences, concise and front-loaded with purpose. Every sentence adds value, though it could be slightly more structured.

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?

Despite no output schema, the description clearly states the return value (path to rendered HTML) and error classification. Failure modes are listed, making it complete for the tool's complexity.

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 baseline is 3. The description does not add per-parameter details beyond what the schema provides, but it contextualizes the overall operation.

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 it renders client-rendered web pages and extracts the full DOM, distinguishing it from sibling tools like figma or other mimic tools that deal with design, knowledge, or build reports.

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?

Explicitly specifies when to use: when a URL returns a JS shell, loading spinner, or hydration scaffold. It doesn't mention alternatives or when not to use, but the instructions are clear enough.

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/miapre/mimic-ai'

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