Skip to main content
Glama

google_maps_search

Search Google Maps to retrieve business listings with rating, reviews, address, phone, website, and hours. Includes follow-up links for reviews, photos, and posts.

Instructions

Returns Google Maps business listings for a search query or a specific place, including rating, reviews, address, phone, website, and operating hours. [Credits: Not explicitly stated on this page (see general Scrapingdog credit pricing).] Notes: Each result item includes ready-made follow-up links: reviews_link, photos_link, and posts_link (each pre-filled with the item's data_id) that map directly to the google_maps_reviews, google_maps_photos, and google_maps_posts endpoints. data_id (format 0xHEX:0xHEX) and place_id (format ChIJ...) are both usable to look up a specific place across the other Maps endpoints. Pagination requires ll to be set. Returns: JSON with search_results array; each item has title, place_id, data_id, data_cid, reviews_link, photos_link, posts_link, gps_coordinates {latitude, longitude}, rating, reviews (count), price, type, types[], address, open_state, operating_hours (per weekday), phone, website, description, thumbnail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
llNoGPS coordinates defining the search origin. Format: @latitude,longitude,zoom/map_height (e.g. @40.7455096,-74.0083012,15.1z). Zoom range: 3z-30z; map height range: 1m-15028132m. Required when using the `page` pagination parameter.
dataNoFilters search results; copied directly from a Google Maps URL. Required for place-specific searches when using type=place. Format: !4m5!3m4!1s[data_id]!8m2!3d[latitude]!4d[longitude].
pageNoPage number of results, incrementing by 20 per page (0 = first page, 20 = second page, etc.). Recommended maximum: 100. The `ll` parameter must be set when paginating. (default: 0)
typeNoSearch type: `search` for query-based results, or `place` for specific location details. Not required when using place_id.
queryYesA Google Maps search query. Example: query=pizza.
domainNoGoogle domain to obtain local results from a specific country, e.g. google.co.in for India, google.co.uk for the UK. See Google Domains Page documentation. (default: google.com)
countryNoTwo-letter country code for the search (e.g. us, uk, fr). See Google Country Parameter documentation for full list. (default: us)
languageNoLanguage of the results (e.g. en, es, fr, de). See Google Language Page documentation for full list. (default: en)
place_idNoUniquely identifies a place on Google Maps (businesses, landmarks, parks, intersections). Can be used independently without any other optional parameters.
Behavior4/5

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

With no annotations, the description carries full burden. It details return format, pagination behavior (requires ll), and notes that each result contains follow-up links. It does not mention any destructive or auth-related behavior, but the tool appears read-only.

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?

The description is well-structured with a clear purpose first, then notes, then return format. It is somewhat long but flows logically, and every sentence adds value. Could be slightly more terse.

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?

Given no output schema, the description fully details the return JSON structure, pagination, and parameter interactions. It addresses complex scenarios like using place_id independently and pagination requirements.

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?

Schema coverage is 100%, and the description adds significant context: format details for ll and data, pagination increments, independent use of place_id, and domain/country/language parameter usage.

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 explicitly states it returns Google Maps business listings including rating, reviews, address, etc. for a search query or specific place. It distinguishes itself from siblings (google_maps_photos, etc.) by noting that it provides follow-up links to those endpoints.

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?

The description explains when to use the tool (search query or place_id), and includes pagination requirements. It implies when to use sibling tools via the follow-up links, but does not explicitly state when not to use this tool or provide alternative scenarios.

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/alessandrobenigni/ScrapingDog-MCP'

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