Skip to main content
Glama
sostag

ScrapingBot MCP Server

by sostag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get the HTML of a page

scrape_raw_html
Read-only

Fetch the raw HTML of any public web page via ScrapingBot proxies, with optional headless Chrome rendering for JavaScript sites and premium proxy support for blocked content.

Instructions

Fetch the HTML source of any public web page through ScrapingBot's proxies. Use useChrome for pages built with JavaScript. Prefer the dedicated tools: scrape_retail for product pages, scrape_real_estate, scrape_booking, scrape_search_engine for Google or Bing, and scrape_social_media for Instagram, TikTok, Facebook, LinkedIn, X/Twitter or Threads (blocked here). Costs 1 credit, 5 with useChrome, 10 with premiumProxy, 25 with both (and for Google pages); failed requests are refunded. Some protected sites always use a premium proxy and cost 10 credits (e.g. amazon.fr, cdiscount.com, fnac.com, leboncoin.fr, seloger.com, rightmove.co.uk, zillow.com). A request blocked by the site is retried once with a premium proxy, billed at the premium price only if it succeeds (the result then says so).

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL of the page, starting with https://
maxCharsNoMaximum number of characters returned. Default 100000.
useChromeNoRender the page with a headless Chrome (JavaScript sites). Default false.
premiumProxyNoUse a premium proxy for sites that block regular proxies. Default false.
proxyCountryNoTwo-letter country code of the proxy (requires premiumProxy), e.g. FR, US.
premiumFallbackNoWhen the site blocks the request, retry it once with a premium proxy, billed at the premium price only if it succeeds. Default true; false turns it off.
waitForNetworkRequestsNoWith useChrome, wait for the page's network requests to finish. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / premiumFallback
      Added value: +{
+  "description": "When the site blocks the request, retry it once with a premium proxy, billed at the premium price only if it succeeds. Default true; false turns it off.",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the credit cost model for each option, refunds on failure, the list of sites that force a premium proxy, and the automatic retry-with-premium-fallback behavior. It does not describe the response shape, but the cost and retry disclosures are exactly the kind of context the annotations cannot carry.

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?

Front-loads purpose and alternates, then the cost model. Dense but every sentence carries routing or billing information; the long single paragraph buries the pricing detail a bit and could be split, but there is no filler.

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, no-output-schema tool, it covers routing, cost, retry semantics, and the special-domain case. The only real gap is that it doesn't describe the return payload (truncation via maxChars is only implied by the schema), but that is minor given the schema's completeness.

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?

Schema coverage is 100% so the baseline is 3; the description adds real meaning by tying useChrome and premiumProxy to concrete cost deltas and flagging which domains trigger premium pricing automatically. The premiumFallback behavior is restated with the billing condition, which reinforces rather than duplicates the schema.

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 resource ('Fetch the HTML source of any public web page') plus the mechanism (ScrapingBot's proxies). It also distinguishes itself from every relevant sibling by name, so an agent can route correctly without opening other schemas.

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?

Explicitly says to prefer dedicated tools and enumerates which ones for which domains (retail, real estate, booking, search engine, social media), and notes social media is blocked here. Clear when-to-use and when-not-to-use.

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