Skip to main content
Glama
sostag

ScrapingBot MCP Server

by sostag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Scrape a product page

scrape_retail
Read-only

Extract structured product data such as title, price, currency, images, brand, stock, and EAN from e-commerce product pages and return JSON for catalog or price monitoring.

Instructions

Extract structured product data (title, price, currency, images, brand, stock, EAN...) from an e-commerce product page such as Amazon, Cdiscount, Fnac or Zalando. Prefer it to scrape_raw_html for any product page. 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.4/5.0
Behavior5/5

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

Goes far beyond the readOnlyHint/openWorldHint annotations: discloses credit pricing per option combination (1/5/10/25), refunds on failure, a named list of sites that force a premium proxy at 10 credits, and an automatic single retry on block with conditional billing that the result reports. These are exactly the cost and side-effect facts an agent needs before spending credits.

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?

Purpose is front-loaded in the first sentence, followed by the cost/retry behavior, which is the right order. The middle section is dense with nested parentheticals (cost tiers, site lists) that take a second read, slightly reducing scannability, but no sentence is redundant.

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?

With no output schema, the description still names the returned fields and the return format ('Returns JSON'), and it covers cost, refund, retry and protected-site behavior. For a 5-parameter, single-endpoint scrape tool with a fully documented schema, nothing material is left for the agent to guess.

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 coverage is 100%, so the schema already documents every parameter's meaning, which sets the baseline at 3. The description adds real value by tying useChrome, premiumProxy, premiumFallback and proxyCountry combinations to their credit costs and describing the fallback billing rule, but it does not elaborate on parameter interactions beyond pricing (e.g., proxyCountry+premiumProxy dependency is only implied).

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+resource ('Extract structured product data ... from an e-commerce product page') and enumerates exactly which fields come back (title, price, currency, images, brand, stock, EAN). It also names concrete target sites and explicitly positions itself above the sibling scrape_raw_html, so the agent can distinguish it without opening either schema.

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?

Gives an explicit routing rule: 'Prefer it to scrape_raw_html for any product page.' That names the alternative and the condition selecting this tool. It stops short of saying when NOT to use it (e.g., product pages on real-estate/booking sites are covered by scrape_real_estate and scrape_booking), so the sibling set is not fully partitioned.

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