Skip to main content
Glama
Sign In

CrawlerData: Google Shopping & SERP

by com.crawlerdata
OverviewDiscussionsAdmin

Google Local

google_local
Read-only

Google local business results: name, rating, reviews, category, address, phone, hours and website, searched from any city-level location. 1 credit.

Input Schema

NameRequiredDescriptionDefault
pageNo
uuleNoAdvanced: a raw Google uule value ("w+...", "a+...", "j+..."), plain or URL-encoded as copied from a Google URL. Use location instead unless you already have uule values.
queryYes
countryNoTwo-letter country code. Defaults to "us", or to the country of location.
languageNoen
locationNoSearch from a city, region or postal code: a Google canonical location name, "City,Region,Country" (Google Ads geotarget format), e.g. "Austin,Texas,United States". When country is omitted it is taken from the location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / uule / description
      Previous value: -"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), sent as is. Use location instead unless you already have uule values."New value: +"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), plain or URL-encoded as copied from a Google URL. Use location instead unless you already have uule values."
    • removedInput schema / properties / uule / pattern
      Removed value: -"^[A-Za-z][+ ][A-Za-z0-9+/_=-]{4,1000}$"
  2. Changed2 schema fields changed
    • changedInput schema / properties / uule / description
      Previous value: -"Advanced: a raw Google uule value, sent as is. Use location instead unless you already have uule values."New value: +"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), sent as is. Use location instead unless you already have uule values."
    • changedInput schema / properties / uule / pattern
      Previous value: -"^[aw][+ ][A-Za-z0-9+/_=-]{4,1000}$"New value: +"^[A-Za-z][+ ][A-Za-z0-9+/_=-]{4,1000}$"
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's addition of the returned fields and the '1 credit' cost is valuable behavioral context. It does not cover pagination limits, empty-result behavior, or any auth requirements, but adds meaningful beyond 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?

A single front-loaded sentence listing key returned fields, scope, and cost with no filler. Every phrase earns its place.

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 the read-only annotations and lack of output schema, the description supplies the important return fields and credit cost. It is slightly incomplete around pagination and non-location parameters, but sufficient for an agent to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the description does little to compensate. It reinforces the city-level location concept but does not explain query, page, language, country defaults, or the advanced uule parameter beyond what the schema already provides.

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 states a specific resource: local business results from Google, including the returned fields. It is distinguishable from sibling tools like google_search and google_news by the 'local business' scope, though it does not explicitly name alternatives.

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 implies usage for local business searches and specifies city-level location scope. However, it gives no explicit guidance on when to prefer this over google_search or other siblings, nor any exclusions.

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

All CrawlerData: Google Shopping & SERP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources