Skip to main content
Glama
sostag

ScrapingBot MCP Server

by sostag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Scrape a grocery product

scrape_grocery
Read-only

Extract grocery product data (title, price, image, brand, nutrition) from a URL. Returns structured JSON for price monitoring or catalog building.

Instructions

Extract a grocery product page (title, price, image, brand, nutritional values). 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?

This description excels in behavioral transparency by disclosing crucial details beyond the annotations, including the tiered cost structure (1, 5, 10, 25 credits), specific site triggers for high cost, and the complex retry/refund logic. This information is essential for financial and operational planning.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely dense and lengthy due to the high volume of operational, financial, and complex behavioral information it must convey. While it is efficient in its density, it sacrifices conciseness.

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?

The definition is highly complete for a complex, high-risk tool. It covers the target data, the costs, the failures (refund policy), the success criteria for retries, and specific geographical exceptions, providing the agent with everything it needs to execute the tool safely and effectively.

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?

Since schema coverage is 100%, the baseline is 3. However, the description adds significant semantic value by explaining the *consequences* and *intent* of parameters like 'premiumProxy' and 'proxyCountry'—that they are required for circumventing site blocks and involve specific cost tiers.

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 tool is clearly defined as scraping grocery products, specifying the data extracted (title, price, image, brand, etc.). The name and title are highly specific and immediately distinguish it from the other scraping tools in the sibling list (e.g., real_estate, booking).

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?

The description provides extensive functional context regarding when and why certain features are necessary (e.g., using premium proxies for blocked sites, using Chrome for JavaScript rendering). While it doesn't explicitly say 'Use this over X,' the functional constraints serve as excellent usage guidelines.

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