Skip to main content
Glama
sostag

ScrapingBot MCP Server

by sostag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Scrape a real estate listing

scrape_real_estate
Read-only

Extract property details like price, rent, surface, rooms, bedrooms, location and images from real estate sites such as SeLoger, Leboncoin, Rightmove or Zillow as structured JSON.

Instructions

Extract a property listing (price or rent, surface, rooms, bedrooms, location, images...) from real estate sites such as SeLoger, Leboncoin, Rightmove or Zillow. 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.6/5.0
Behavior5/5

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

The description goes far beyond annotations by detailing complex behaviors: pricing schemes, refund policies for failed requests, and the specific billing outcome of the retry mechanism for blocked sites. This operational knowledge is critical.

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?

While the description is detailed and lengthy, it is highly dense with value. It avoids fluff, with every sentence providing necessary operational constraints, such as cost or technical limitations.

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

Completeness5/5

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

Given the complexity of the tool (multiple optional parameters, pricing structure, and varied site requirements), the description is complete, providing all necessary behavioral and cost contexts required for safe and effective tool invocation.

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?

Although schema coverage is 100%, the description adds necessary semantic depth by explaining how certain parameters like `premiumProxy` and `premiumFallback` interact with site policies, retry success, and billing outcomes.

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 is explicit, stating it extracts data like price, surface, rooms, and location specifically from real estate sites (SeLoger, Zillow). It clearly defines the tool's resource and core function.

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 defines operational boundaries by mentioning specific supported sites (SeLoger, Rightmove) and warns that certain sites necessitate premium proxies, guiding the agent on when specific configurations are required.

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