Skip to main content
Glama

ScraperAPI (Unofficial)

Scraperapi Google Search

scraperapi_google_search
Read-onlyIdempotent

Run a Google search and get structured SERP results, organic results, titles, links, snippets, and related data. Example: scraperapi_google_search({ query: "best running shoes 2026", country_code: "us", tld: "com", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "best running shoes 2026",
      "_apiKey": "your-scraperapi-api-key"
    },
    "name": "scraperapi_google_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldNoGoogle top-level domain, e.g. "com", "co.uk". Optional (default com).
queryYesThe Google search query, e.g. "best running shoes 2026"
_apiKeyYesScraperAPI key
country_codeNoTwo-letter country code for geotargeting the search, e.g. "us". Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the safety profile is covered. The description adds the return shape (structured SERP plus organic fields) and implies an API key requirement via the example, but says nothing about credit consumption, result counts, rate limits, or error behavior.

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?

Two sentences with the capability stated first and the example second, so an agent gets the core behavior immediately. The example is somewhat redundant with the schema's own examples but is not harmful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does carry the burden of describing return values, and it names the main result fields. It stops short of explaining result volume, pagination, or request cost, which matter for a proxy-scraping search call.

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 description coverage is 100%, so all four parameters, including tld and country_code defaults, are already documented. The description adds no semantics beyond the schema, and its example only repeats values already present in the schema examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Run a Google search") and enumerates the return content (SERP results, organic results, titles, links, snippets). An agent can distinguish this from the Amazon search sibling by the explicit "Google" scope, though no sibling is named.

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

Usage Guidelines2/5

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

Provides only a sample invocation, with no statement of when to prefer this over alternatives such as scraperapi_scrape or search_within, and no exclusions or prerequisites beyond the API key appearing in the example. Usage context is entirely inferred from the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.