Skip to main content
Glama

Scrapingdog

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Scrapingdog Scrape

scrapingdog_scrape
Read-onlyIdempotent

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" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe full URL to scrape including protocol, e.g. "https://example.com/page"
waitNoMilliseconds to wait for the page to load (0–35000). Use together with dynamic:true for slow pages.
formatNoResponse format: "markdown" for LLM-friendly text, "links" for a link list, otherwise HTML (default). Options: html, markdown, links, summary.
_apiKeyYesBYOK Scrapingdog API key (free trial at scrapingdog.com)
countryNoISO 3166-1 alpha-2 country code to proxy from, e.g. "us", "gb", "de". Optional geotargeting.
dynamicNoRender JavaScript in a headless browser before returning content (use for SPAs / dynamic pages). Costs 5 credits per request instead of 1 (25 with premium proxies). Default false.
premiumNoUse premium residential proxies for hard-to-scrape sites. Costs 10 credits (25 combined with dynamic:true). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-scrapingdog-api-key",
+    "url": "https://example.com"
+  },
+  {
+    "_apiKey": "your-scrapingdog-api-key",
+    "dynamic": true,
+    "format": "markdown",
+    "url": "https://example.com/dynamic-page",
+    "wait": 5000
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses credit costs for different options (dynamic, premium), format output defaults, and rendering behavior. Provides behavioral context beyond annotations, which already indicate read-only, idempotent, and non-destructive operations.

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

Conciseness5/5

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

Single paragraph, front-loaded with core action, then options, then example. Every sentence adds information; no redundancy or fluff.

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?

Returns HTML or markdown as stated, but lacks detail on error handling or response structure. No output schema, but the tool's behavior is sufficiently described for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant value beyond the input schema by explaining credit costs for dynamic and premium, and giving a full example. Schema coverage is 100%, but the description enriches parameter understanding.

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?

Clearly states that the tool scrapes websites via rotating proxies, returns HTML or markdown, and offers dynamic rendering. Distinguishes from more specialized sibling tools like scrapingdog_amazon_product and scrapingdog_google_search.

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?

Explains when to use dynamic (SPAs), premium (hard-to-scrape), and country (geotargeting). Includes an example. Does not explicitly state when to use sibling tools instead, but the general-purpose nature is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Scrapingdog toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources