Skip to main content
Glama
AceDataCloud

mcp-webextrator

by AceDataCloud

webextrator_render

Render any web page with a headless browser to capture the fully rendered HTML after JavaScript execution, enabling inspection of dynamic content and single-page apps.

Instructions

Render a web page and return the fully rendered HTML.

Uses a headless browser to navigate to the specified URL, waits for JavaScript
to execute, and returns the final rendered HTML source.

Use this when:
- You need the fully rendered HTML of a JavaScript-heavy page
- You want to inspect the DOM after dynamic content has loaded
- You need to capture single-page application (SPA) content

Returns:
    By default, the rendered HTML content inline. With mode="async", a JSON
    envelope with a `task_id` — poll `webextrator_get_task` until it reports
    `finished_at`, then read the rendered HTML from its `response`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the web page to render. Required.
modeNoProcessing mode. Defaults to API sync behavior. Pass 'async' to return immediately with a task_id to poll via webextrator_get_task.
delayNoExtra delay in seconds after page load before capturing HTML.
cookiesNoCookies to install before navigation. Each cookie is an object with at least 'name' and 'value', plus optional 'domain', 'path', 'expires', 'httpOnly', 'secure', 'sameSite'. Useful for authenticated pages.
headersNoExtra HTTP headers to include with the page request.
timeoutNoTotal timeout in seconds for page load. Default is 30.
user_agentNoOverride the User-Agent header for the page request.
wait_untilNoPage load wait condition before capturing HTML. Options: 'load', 'domcontentloaded', 'networkidle', 'commit'. Default is 'networkidle'.
bypass_cacheNoSkip the Redis result cache for this request (still writes the fresh result back). Default is false.
callback_urlNoCallback URL for async processing. If provided, the task runs asynchronously and results are sent to this URL when complete.
block_resourcesNoResource types to block during page load to speed up rendering. Options: 'image', 'font', 'media', 'stylesheet', 'xhr', 'fetch'.
cache_ttl_secondsNoOverride the global cache TTL (seconds) for this entry. 0 means do not cache this response. Default is 3600.
wait_for_selectorNoCSS selector to wait for before capturing HTML.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description bears full responsibility for disclosure. It reveals key behaviors: uses a headless browser, waits for JavaScript execution, and returns rendered HTML. It also transparently describes the async flow (returns task_id, poll until finished_at, read response). It does not cover side effects like network requests, SSRF risks, or failure modes, but what it discloses is accurate and useful.

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?

The description is tight and well-organized: an opening action sentence, a 'Use this when' bulleted list, and a Returns section. No filler or redundant phrases. It front-loads the core purpose and only then adds usage guidance and output details, all in under 120 words.

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?

The tool is complex with 13 parameters, async behavior, caching, and multiple options, yet the description covers the essential workflow well. It explains the sync/async difference, the return types, and typical use cases. It does not mention caching or resource blocking, but these are fully documented in the schema and an output schema exists, so the description is sufficiently complete for selection and initial invocation.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds meaningful context beyond the schema by explaining the 'mode' parameter's impact (async returns a JSON envelope with task_id), and by clarifying how to consume the output. The 'Returns:' section is a valuable addition that ties parameters to expected results.

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 opens with a specific verb and resource: 'Render a web page and return the fully rendered HTML.' It clearly states the tool's function and effectively distinguishes from siblings like webextrator_extract and webextrator_get_task by mentioning dynamic content, DOM inspection, and SPA capture. This is a textbook example of purpose clarity.

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 includes an explicit 'Use this when:' section listing three concrete scenarios, which provides clear context for when the tool is appropriate. It also explains the async mode and directs users to poll with webextrator_get_task. However, it does not explicitly state when *not* to use the tool or name alternative tools as substitutes, so it misses the full 'when-not/alternatives' bar.

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/AceDataCloud/WebExtratorMCP'

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