Skip to main content
Glama

google_local

Retrieve Google Local business listings including ratings, reviews, addresses, GPS coordinates, and business type using search query and location parameters.

Instructions

Retrieves Google Local business listings including ratings, reviews, addresses, GPS coordinates, and business type. Costs 5 API credits per request. [Credits: 5 API credits per request] Notes: location and uule are mutually exclusive. Returns: { local_results: [{title, rating, reviews, price, description, address, type, place_id, gps_coordinates: {lat, lng}}] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tbsNoAdvanced parameter ('to be searched') to filter search results.
pageNoPage number of Google search results. 0 = first page, 1 = second page, etc. (default: 0)
uuleNoEncoded geographic location/locale to tailor results, e.g. w+CAIQIFJlbWF5IFN0YXRlcw==. Cannot be used together with `location`.
queryYesGoogle Search query, e.g. query=coffee+in+manhattan.
domainNoGoogle domain for local results, e.g. google.co.in for India, google.co.uk for the UK. (default: google.com)
countryNoISO country code from which to seek Google search results. (default: us)
ludocidNoGoogle My Business listing ID (CID), also known as the Google Place ID, to scrape.
languageNoLanguage of the results, e.g. en, es, fr, de. (default: en)
locationNoLocation from which to scrape local results, e.g. 'Manhattan, New York'. Cannot be used together with `uule`.
Behavior3/5

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

With no annotations, the description carries the burden. It discloses credit cost and mutual exclusivity but lacks details on authentication, rate limits, error handling, or pagination beyond the 'page' parameter.

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 concise with a clear first sentence stating purpose, followed by credits and notes. The structure is good, though the credits line is redundant.

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 9 parameters and no output schema, the description provides a reasonable return structure and constraints. However, it misses potential error scenarios and pagination behavior beyond the 'page' parameter.

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 coverage is 100%, so the schema already documents parameters. The description adds critical mutual exclusivity note and return format, which goes beyond the schema.

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?

The description clearly states it retrieves Google Local business listings with specific fields like ratings, reviews, addresses, etc. It distinguishes from siblings like google_search (web search) but does not explicitly differentiate from similar tools like google_maps_search.

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 mentions cost (5 credits) and the mutual exclusivity of 'location' and 'uule', providing some constraints. However, it does not provide when to use this tool versus alternatives like google_maps_search.

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