Skip to main content
Glama
sostag

ScrapingBot MCP Server

by sostag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Scrape a travel page

scrape_booking
Read-only

Extract hotel or rental listing and search-result data from Booking.com, Airbnb, Expedia, Hotels.com, or Abritel by URL. Returns structured JSON for prices, images, ratings, and rooms.

Instructions

Extract a hotel or rental page (title, price, images, rating, rooms) or a search results page from Booking.com, Airbnb, Expedia, Hotels.com or Abritel. Put the stay dates in the URL. Returns JSON. 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://
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.

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
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses credit costs, cost modifiers for useChrome and premiumProxy, refund behavior, protected-site billing, and automatic premium-proxy retry semantics. These are material operational details an agent could not infer from the schema.

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 purpose and supported sites are front-loaded, followed by URL date guidance, return format, and billing behavior. It is dense but every major clause is useful, though the long list of protected-site examples could be tightened.

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 scraping tool with no output schema, the description explains the JSON return and some fields, plus billing and retry behavior. Search-result return shape and pagination are not covered, leaving a small completeness gap.

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, but the description adds meaning by mapping useChrome and premiumProxy to specific credit costs and explaining premiumFallback billing. It does not add much for proxyCountry, but that parameter is already documented.

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 gives a precise verb ('Extract') and resource ('hotel or rental page... or a search results page') and names the exact travel sites covered. This clearly separates it from the retail, grocery, social, and real-estate siblings by domain.

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?

It provides clear usage context by naming supported travel sites and instructing users to put stay dates in the URL. It does not explicitly compare against alternatives such as scrape_raw_html or scrape_real_estate, but the domain context is strong.

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