Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official
by scraperapi
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

google_search

Read-onlyIdempotent

Retrieve parsed Google Search results as structured JSON. Get organic results, ads, knowledge panels, and pagination for any query without scraping HTML.

Instructions

Retrieve parsed Google Search (SERP) results for a query.

    Returns the organic results, ads, related searches, knowledge panels, and
    pagination for a Google web search — already parsed into structured JSON —
    without you having to scrape and parse the SERP HTML yourself.

    When to use:
    - Programmatic SERP data: rankings, titles, links, snippets for a keyword
    - SEO/rank tracking, competitive research, or answer-engine grounding
    - Time- or date-bounded searches (recent news-like results, date ranges)

    When NOT to use:
    - Fetching the content of a specific known URL (use the 'scrape' tool)
    - Google News, Jobs, Shopping, or Maps — use the dedicated tool for each

    Args:
        params (GoogleSearchParams): query (required) plus optional
            localization (country_code, gl, hl, uule), pagination (num, start),
            date filters (date_range_start/end, time_period), tld, output_format,
            include_html, and tbs.

    Returns:
        str: JSON (default) or CSV containing the structured search results.

    Raises:
        ToolError: If the API key is missing, the rate limit is exceeded, or
            the request fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Describes returns (JSON/CSV parsed), error conditions (missing API key, rate limits), and reinforces readOnlyHint=true by framing as retrieval. No contradiction with 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?

Well-organized into sections: main purpose, usage guidelines, args, returns, raises. Every sentence earns its place; no redundancy.

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?

Covers purpose, usage, parameters, return format, and errors. With output schema and annotations, the description provides all necessary context for an agent.

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?

Schema description coverage is high (nested params have descriptions). The description adds value by grouping optional parameters into categories (localization, pagination, date filters) and noting required query, though detailed semantics are already in the schema.

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 states it retrieves parsed Google Search results, lists specific components (organic results, ads, knowledge panels), and distinguishes from sibling tools by referencing dedicated tools for News, Jobs, Shopping, and Maps.

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

Usage Guidelines5/5

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

Explicit 'When to use' and 'When NOT to use' sections with concrete examples: use for SERP data, SEO, rank tracking; not for specific URL scraping or other Google verticals. Includes alternatives like 'scrape' and dedicated tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scraperapi/scraperapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server