Skip to main content
Glama

render_webpage

Forced headless Chromium browser renderer for JavaScript-heavy SPAs and dynamic webpages. Always executes Tier 3 isolated browser rendering and returns the post-JS rendered HTML DOM alongside extracted text, Markdown, links, and metadata. Do not use for PDFs or static pages (use fetch_webpage instead).

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": "render_webpage"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS webpage URL for forced headless browser rendering.
scrollNoScroll down to trigger lazy-loaded content before extraction.
wait_msNoOptional extra wait in milliseconds (0-5000) after page load.
max_charsNoMaximum characters returned for content, Markdown, and HTML.
dismiss_cookiesNoAttempt to dismiss cookie/GDPR banners before extraction.
only_main_contentNoExtract only main article/content (strips nav, footer, aside).
wait_for_selectorNoOptional CSS selector to wait for before extraction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / dismiss_cookies
      Added value: +{
      +  "default": true,
      +  "description": "Attempt to dismiss cookie/GDPR banners before extraction.",
      +  "title": "Dismiss Cookies",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / only_main_content
      Added value: +{
      +  "default": true,
      +  "description": "Extract only main article/content (strips nav, footer, aside).",
      +  "title": "Only Main Content",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / scroll
      Added value: +{
      +  "default": false,
      +  "description": "Scroll down to trigger lazy-loaded content before extraction.",
      +  "title": "Scroll",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / wait_for_selector
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 256,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional CSS selector to wait for before extraction.",
      +  "title": "Wait For Selector"
      +}
    • addedInput schema / properties / wait_ms
      Added value: +{
      +  "default": 0,
      +  "description": "Optional extra wait in milliseconds (0-5000) after page load.",
      +  "maximum": 5000,
      +  "minimum": 0,
      +  "title": "Wait Ms",
      +  "type": "integer"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / max_chars / description
      Added value: +"Maximum characters returned for content, Markdown, and HTML."
    • addedInput schema / properties / url / description
      Added value: +"Public HTTP or HTTPS webpage URL for forced headless browser rendering."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the rendering tier ('Tier 3 isolated browser rendering'), that rendering is always forced, and that the output includes post-JS DOM plus text, Markdown, links, and metadata. It stops short of noting cost/timeouts, anti-bot blocking, or rate limits, which are the main behavioral risks for headless rendering.

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?

Three sentences, front-loaded with the capability, then the return contract, then the exclusion rule. No filler or restatement of the name.

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?

For a 7-parameter rendering tool with no output schema, the description explains both what is returned and the key selection rule. The only material gap is failure behavior — what happens when rendering times out or a bot wall blocks the page — which an agent would benefit from knowing.

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 every parameter including scroll, wait_ms, dismiss_cookies and only_main_content is already documented in the schema. The description adds no parameter-level guidance (e.g. when to enable scroll or raise wait_ms), so the baseline 3 applies.

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?

States a specific verb and mechanism ('Forced headless Chromium browser renderer') and an explicit target class ('JavaScript-heavy SPAs and dynamic webpages'), plus names what it returns. The final sentence distinguishes it from fetch_webpage by exclusion, so an agent can pick it without opening a schema.

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

Usage Guidelines5/5

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

Gives both a when-to-use condition (JS-heavy SPAs, dynamic pages) and an explicit when-not (PDFs, static pages) with a named alternative (fetch_webpage). That is the full when/when-not/alternative triad.

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.