Skip to main content
Glama

Scrapingdog

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Scrapingdog Google Search

scrapingdog_google_search
Read-onlyIdempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page number, 0-based: 0 = first page, 1 = second page. Default 0.
queryYesThe Google search query, e.g. "best running shoes 2026". Supports operators like site: and intitle:.
domainNoGoogle domain to search, e.g. "google.co.uk", "google.co.in". Default "google.com".
_apiKeyYesBYOK Scrapingdog API key (free trial at scrapingdog.com)
countryNoTwo-letter country code to localize results, e.g. "us", "gb", "fr". Default "us".
resultsNoNumber of results to return per page, e.g. 10. Optional.
languageNoResults language code, e.g. "en", "es", "fr". Default "en".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-scrapingdog-api-key",
+    "query": "best running shoes 2026"
+  },
+  {
+    "_apiKey": "your-scrapingdog-api-key",
+    "country": "gb",
+    "page": 0,
+    "query": "site:example.com machine learning"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false. The description adds value by revealing the 5-credit cost per search and summarizing the output structure (organic results, related searches, PAA), which are beyond the annotations.

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?

The description is extremely concise: two sentences and an example, all front-loaded with essential information. Every word serves a purpose, no redundancy.

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?

Given 7 parameters, no output schema, and strong annotations, the description covers purpose, cost, output fields, and provides an example. It lacks details on error handling or rate limits, but the annotations cover idempotency and safety. Overall, it is sufficiently complete for the tool's complexity.

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 each parameter has a description in the schema. The description provides an example using query, country, and _apiKey, which adds contextual usage but does not explain parameters further. Baseline of 3 is appropriate as the description does not compensate for low coverage.

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 clearly identifies the tool as a Google SERP API via Scrapingdog, specifying the action (run a search), resource (Google search), and output (structured organic results, related searches, people-also-ask questions). This distinguishes it from sibling tools like scrapingdog_amazon_product or scrapingdog_scrape.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for Google searches and mentions a credit cost, but does not explicitly state when to use this tool over alternatives or provide exclusions. The sibling list offers differentiation by name, but no direct guidance is given.

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