Skip to main content
Glama
AceDataCloud

mcp-webextrator

by AceDataCloud

webextrator_render

Render a web page in a headless browser to obtain the fully rendered HTML after JavaScript execution, ideal for capturing dynamic content from JavaScript-heavy sites and single-page applications.

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:
    JSON response containing the rendered HTML content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the web page to render. Required.
modeNoProcessing mode. 'sync' (default) waits for the result; 'async' returns immediately with a task_id to poll via the Tasks API.
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 carries full responsibility for disclosing behavior. It explains the headless browser rendering, JavaScript execution, sync/async modes, caching options, and resource blocking. It does not discuss error handling, rate limits, or potential side effects, but for a read-only render tool, the coverage is good.

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 well-structured: a concise opening sentence, bullet points for usage guidance, and a return statement. Despite the complexity of 13 parameters, it remains focused and front-loaded with the core behavior. It could be slightly more concise, but it earns a 4.

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?

Given the tool's complexity (13 parameters, sync/async modes, caching) and the presence of an output schema to detail return values, the description adequately covers the main behavior and constraints. It does not discuss edge cases or error handling, but for a rendering tool, the information is complete enough for effective use.

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 coverage is 100% with all 13 parameters described in the input schema. The description adds value by explaining the high-level purpose of the tool and mentioning the return format, but it does not significantly enhance parameter understanding beyond the schema. Baseline 3 is appropriate.

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 starts with 'Render a web page and return the fully rendered HTML', which is a clear verb+resource statement. It further explains the use of a headless browser and JavaScript execution, distinguishing it from sibling tools like 'webextrator_extract' which likely extracts specific data. The 'Use this when' bullets reinforce the purpose.

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 explicit 'Use this when' bullets that list three scenarios, providing clear context for appropriate use. However, it does not explicitly state when not to use the tool or mention alternatives, though sibling tool names imply other capabilities. This is a minor gap from a 5.

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