Skip to main content
Glama

Browser-Rendered Page HTML

web.scrape.browser
Read-onlyIdempotent

Render JavaScript-heavy pages with a headless browser to return fully rendered HTML, ideal for SPAs, React, Vue, or dynamic content that raw HTTP cannot capture.

Instructions

⚡ ACTION: Render a URL with headless browser and return JS-rendered HTML. Use for SPAs, React/Vue apps, or pages with dynamic content that raw HTTP cannot capture. Returns fully rendered DOM as HTML text (Zyte)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to render with headless browser — returns JS-rendered HTML. Use for SPAs, dynamic content. More expensive than extract. Example: "https://example.com"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations already declare safe reads (readOnlyHint, no destruction); description adds context about headless browser rendering and JS execution, which is useful and consistent with annotations. No contradictory information.

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?

Description is extremely concise: three short sentences with emoji for attention, front-loading action and purpose, then usage guidance, then output. No wasted words.

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?

Given the tool has an output schema (not shown but indicated in context), the description adequately covers action, use case, and output format. For a single-parameter tool with clear behavior, this is complete.

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 has 100% coverage for the single 'url' parameter, with description repeating tool purpose. The tool description adds no new parameter-specific semantics beyond what the schema provides, justifying the baseline score.

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 action ('Render a URL with headless browser'), the resource ('JS-rendered HTML'), and distinguishes from raw HTTP and sibling tools like 'web.scrape.extract' by specifying use for SPAs and dynamic content.

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 says to use for SPAs, React/Vue apps, or dynamic content, and implies not to use when raw HTTP suffices. It could be improved by directly naming alternative tools like 'web.scrape.extract'.

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/whiteknightonhorse/APIbase'

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