Loading ToolBench
Wraps Scrapingdog (scrapingdog.com), a proxy-based web scraping API with structured endpoints for Google SERP and Amazon products.
Three tools with complete input schemas and descriptions. Naming follows verb_noun pattern (scrapingdog_scrape, scrapingdog_google_search, scrapingdog_amazon_product). Descriptions are detailed (150-250 chars) and include examples. However, output schemas are NOT documented, LLMs cannot predict response structure. Parameters lack enums for constrained values (format, country codes). The _apiKey parameter violates secret-injection pattern by appearing as a tool parameter instead of server-side injection. No error handling guidance. Missing per-parameter type constraints (e.g., country must be ISO 3166-1 alpha-2, wait must be 0-35000).
Get Amazon product data by ASIN via Scrapingdog — title, price, rating, review count, availability, feature bullets, and images as parsed JSON. Pass an asin (e.g. "B0BFC7WQ6R") or a full Amazon product url. Example: scrapingdog_amazon_product({ asin: "B0BFC7WQ6R", domain: "com", _apiKey: "your-key" })
Google SERP API — run a Google search via Scrapingdog and get structured results: parsed organic results (title, link, snippet), related searches, and people-also-ask questions. Costs 5 credits per search. Example: scrapingdog_google_search({ query: "best running shoes 2026", country: "us", _apiKey: "your-key" })
Scrape any website through Scrapingdog's rotating proxies and return its content. Returns HTML by default, or clean markdown with format:"markdown" (ideal for feeding an LLM). Set dynamic:true to render JavaScript in a headless browser for SPAs and dynamic pages (costs 5 credits instead of 1), premium:true for hard-to-scrape sites (residential proxies, 10 credits), and country to geotarget the proxy. Example: scrapingdog_scrape({ url: "https://example.com", format: "markdown", dynamic: true, _apiKey: "your-key" })
Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination). Breaks tool-chaining and forces agents to guess at downstream parameter mappings.
API key exposed as _apiKey tool parameter. Violates secret-injection pattern, credentials in tool params leak into agent logs and prompt history. Must use server-side environment variable injection.
Constrained parameters lack enums. 'format' accepts html|markdown|links|summary but is free-form string. 'country' expects ISO 3166-1 alpha-2 but no enum. LLMs will hallucinate invalid values.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
No error handling guidance. Tool descriptions lack recovery hints (e.g., 'If unauthorized, verify API key at scrapingdog.com'). Agents cannot self-correct on failures.
Numeric parameter constraints not enforced in schema. 'wait' accepts 0-35000ms but no minValue/maxValue. 'page' and 'results' unbounded. LLMs can pass absurd values.