Skip to main content
Glama
AceDataCloud

mcp-webextrator

by AceDataCloud

webextrator_render

Render web pages with JavaScript execution and return fully rendered HTML. Capture dynamic content from single-page applications and JavaScript-heavy sites.

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.
delayNoExtra delay in seconds after page load before capturing HTML.
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'.
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'.
wait_for_selectorNoCSS selector to wait for before capturing HTML.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It mentions headless browser usage and JavaScript execution but does not discuss side effects like resource consumption, potential permissions, or rate limits. This is adequate but not comprehensive.

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 concise (5 sentences) and well-structured with a clear opening, bullet-pointed usage guide, and return value statement. Every sentence adds value without redundancy.

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 presence of an output schema (assumed to document return format), the description adequately covers purpose and usage context for a rendering tool. It could mention potential delays or resource blocking, but overall it is sufficient.

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 the input schema already documents all parameters. The tool description adds no additional parameter details beyond what is in the schema, resulting in a baseline score of 3.

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 tool renders a web page using a headless browser and returns fully rendered HTML. It uses specific verbs ('render', 'navigate', 'capture') and distinguishes from sibling tools like 'webextrator_extract' by focusing on 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?

The description provides explicit use cases (JavaScript-heavy pages, SPA content) and a 'Use this when' section. However, it does not mention when not to use this tool or provide alternatives, which would improve guidance.

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