Skip to main content
Glama

Browser render

browser_render
Read-onlyIdempotent

Headless browser render any public URL with JavaScript executed in sandboxed Chromium: returns rendered HTML (up to 200,000 chars), visible text, title, headings, and links (or Markdown). $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "browser_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL to render in headless Chrome.
formatNoOptional output format: both (default HTML + text), html, text, or markdown.
waitMsNoOptional post-load JS settle wait in ms (0-3000, default 1200).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: a $0.003 per-call cost, the payment rails (USDC on Arc/Base/Solana, XNT on X1), sandboxed Chromium execution, and a 200,000-char output cap. The two-phase x402 flow is disclosed, which is the key behavioral wrinkle the annotations do not cover. It stops short of describing failure modes for blocked or unreachable pages.

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?

Two sentences, front-loaded with what the tool does and what it returns before moving to pricing and the payment protocol. The parenthetical currency list is slightly dense but each clause carries information the agent needs.

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?

No output schema exists, and the description compensates by enumerating return fields and the 200,000-char ceiling. Together with cost, payment flow, and format options, an agent has enough to call it correctly; only error/blocked-page behavior and truncation handling are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the meaning of `payment` operationally (call without it to get terms, with it to pay) and by noting the Markdown output option. It does not elaborate on url or waitMs beyond what the schema already states, which is acceptable given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Headless browser render any public URL with JavaScript executed in sandboxed Chromium") and enumerates outputs (rendered HTML, visible text, title, headings, links, or Markdown). The JS-execution and output list distinguish it functionally from static-conversion siblings, but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage guidance for the payment handshake ("Call once without `payment` for terms, then call again with `payment`"), which is the non-obvious part of invoking this tool. However, it offers no guidance on when to prefer this over alternatives like page_extract, web_read, or page_markdown, which are the calls an agent would most plausibly confuse it with.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources