Skip to main content
Glama
Sign In
webscraping-ai

WebScraping-AI MCP Server

Official
by webscraping-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Page HTML

webscraping_ai_html
Read-only

Fetch the full rendered HTML of a web page, including JavaScript-rendered content, to scrape dynamic sites and extract web data.

Instructions

Get the full rendered HTML of a web page (with JavaScript execution by default). API docs: https://webscraping.ai/docs#html

Input Schema

NameRequiredDescriptionDefault
jsNoExecute on-page JavaScript using a headless browser (false by default).
urlYesURL of the target page.
proxyNoType of proxy: datacenter, residential, or stealth (datacenter by default). Residential and stealth requests cost more than datacenter — see the pricing page.datacenter
deviceNoType of device emulation.
formatNoResponse format (json or text).
countryNoCountry of the proxy to use (US by default).
timeoutNoMaximum web page retrieval time in ms (20000 by default, maximum is 30000).
wait_forNoCSS selector to wait for before returning the page content.
js_scriptNoCustom JavaScript code to execute on the target page.
js_timeoutNoMaximum JavaScript rendering time in ms (3000 by default).
custom_proxyNoYour own proxy URL in "http://user:password@host:port" format.
error_on_404NoReturn error on 404 HTTP status on the target page (false by default).
error_on_redirectNoReturn error on redirect on the target page (false by default).
return_script_resultNoReturn result of the custom JavaScript code execution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / proxy / description
      Previous value: -"Type of proxy: datacenter, residential, or stealth (datacenter by default). Use residential if the site restricts datacenter traffic, or stealth for the most heavily protected sites with advanced anti-bot detection. Residential and stealth requests cost more than datacenter — see the pricing page."New value: +"Type of proxy: datacenter, residential, or stealth (datacenter by default). Residential and stealth requests cost more than datacenter — see the pricing page."
  2. Changed1 schema field changedv1.2.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changedv1.0.5
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "us",
-  "gb",
-  "de",
-  "it",
-  "fr",
-  "ca",
-  "es",
-  "ru",
-  "jp",
-  "kr",
-  "in"
-]New value: +[
+  "us",
+  "gb",
+  "de",
+  "it",
+  "fr",
+  "ca",
+  "es",
+  "ru",
+  "jp",
+  "kr",
+  "in",
+  "hk",
+  "tr"
+]
  4. Changed2 schema fields changedv1.0.4
    • changedInput schema / properties / proxy / description
      Previous value: -"Type of proxy, datacenter or residential (datacenter by default)."New value: +"Type of proxy: datacenter, residential, or stealth (datacenter by default). Use residential if the site restricts datacenter traffic, or stealth for the most heavily protected sites with advanced anti-bot detection. Residential and stealth requests cost more than datacenter — see the pricing page."
    • changedInput schema / properties / proxy / enum
      Previous value: -[
-  "datacenter",
-  "residential"
-]New value: +[
+  "datacenter",
+  "residential",
+  "stealth"
+]
  5. Addedv1.0.2

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly/openWorld/non-destructive, so safety needs no restating, but the description's parenthetical '(with JavaScript execution by default)' directly conflicts with the schema, where the `js` parameter defaults to false. That misstatement can cause an agent to assume rendering when it will not happen, and the description adds nothing about credits, proxy cost, or rate limits for a paid scraping call.

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 short sentences, capability front-loaded, docs link appended with no filler. It is tight, though the misleading default claim and the absence of any hint about the 13 optional parameters leave the sentence budget underused.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 parameters, no output schema, and no annotations explaining cost or auth, the description is far too thin: it never says what the returned HTML looks like, whether errors surface as HTTP errors, how `format` changes the response shape, or that residential/stealth proxies cost extra. It also mismatches the schema on JS rendering, so an agent cannot call it correctly from the description alone.

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

Parameters2/5

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

Schema description coverage is 100%, so the schema alone earns a baseline 3, but the description does not merely stay silent — it asserts a JS default that contradicts the documented `js` default of false. For a 14-parameter tool the description adds no orienting detail (which params matter, cost implications of `proxy`, timeout ceiling), and its one parameter claim is misleading.

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 ('Get the full rendered HTML of a web page') and signals the JS-rendering aspect, which distinguishes it from the plain-text siblings in spirit. However, it never names webscraping_ai_text, webscraping_ai_selected, or webscraping_ai_fields, so the agent must infer the HTML-vs-extracted-content boundary from names alone.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the nine sibling scrapers, no when-not conditions, and no mention of prerequisites such as API key or credit consumption. The only routing aid is a docs URL, which an agent cannot reliably follow mid-task.

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

Deploy Server

Other Tools