Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

google_maps_search

Read-onlyIdempotent

Retrieve structured local business results from Google Maps. Provide a query and coordinates to get name, address, rating, and reviews count for building datasets or competitive analysis.

Instructions

Retrieve parsed Google Maps place/business results for a query.

    Returns structured local business/place results (name, address, rating,
    reviews count, category, coordinates) from Google Maps for a query,
    optionally centered on a latitude/longitude and zoom level.

    When to use:
    - Local business discovery ('coffee shops in Austin')
    - Building local listings datasets; location-based competitive research

    When NOT to use:
    - Non-local web results (use 'google_search')
    - Driving directions or routing (not provided by this endpoint)

    Args:
        params (GoogleMapsSearchParams): query, latitude, and longitude are
            required; optional zoom, country_code, tld, output_format, and
            include_html.

    Returns:
        str: JSON (default) or CSV containing the structured maps 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
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds context: returns parsed structured results, can raise ToolError for missing API key or rate limits, and mentions output format options.

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?

Well-structured with sections, front-loaded with main purpose, but could be slightly more concise. Every sentence contributes meaning.

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?

Covers usage, return format, error cases, and optional params. Output schema exists, so return values not needed. Annotations cover safety. Fairly complete for a search tool.

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 has low description coverage (0% per context), but description lists required params (query, latitude, longitude) and mentions optional ones (zoom, tld, etc.) without detail. Partially compensates.

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 the tool retrieves parsed Google Maps place/business results, with a specific verb and resource. It distinguishes from siblings like google_search by noting it's for local results, not non-local web results.

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 examples (e.g., 'coffee shops in Austin') and alternatives (google_search for non-local results, not for directions).

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