Skip to main content
Glama

Google Business Profile and reviews

search_get_local
Read-only

Local SEO from Google Business Profile: Maps and Search impressions, calls, website clicks, direction requests, chats and bookings vs the prior period, review rating, new reviews, response rate and the unanswered (lowest-rated first) reviews, per location. Use for local SEO, Google Maps, Business Profile, GMB, reviews or "how many calls/directions".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_get_local"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
daysNo
limitNo
actionNo
statusNo
date_toNo
page_idNo
sort_byNo
user_idNo
site_urlNo
client_idNo
date_fromNo
ad_accountNo
ig_user_idNo
user_emailNo
range_presetNo
activity_onlyNo
campaign_nameNo
property_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, and the description adds the comparative framing ('vs the prior period') plus the ordering of unanswered reviews (lowest-rated first). It says nothing about quotas, latency, permissions, or what happens when a location has no Business Profile data — gaps that matter for a 19-parameter reporting call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with the metric list up front, which is good structure, but the trailing trigger-word list reads as keyword stuffing and the sentence is dense enough that the review-specific behavior is buried mid-clause. Nothing is wasted outright, yet the density hurts scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter tool with zero schema description coverage, the description should orient the agent toward the handful of parameters that actually shape the query; instead it leaves all of them undocumented. An output schema exists so return values need not be explained, and annotations cover the safety profile, but the input side is a serious hole.

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 0% across 19 parameters, so the description carries the full explanatory burden — and it explains none of them. Only the loosest hints exist ('per location' for page_id/client_id, 'vs the prior period' for days/date_from/date_to/range_preset), while action, status, sort_by, limit, activity_only, ad_account, ig_user_id and campaign_name are left entirely opaque.

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 names a specific resource (Google Business Profile local SEO) and enumerates the concrete metrics returned: impressions, calls, website clicks, direction requests, chats, bookings, review rating, new reviews, response rate and unanswered reviews. An agent can tell this is the local/GMB surface rather than generic web metrics, though it never names a sibling to contrast with.

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?

It gives positive triggers — 'Use for local SEO, Google Maps, Business Profile, GMB, reviews or how many calls/directions' — which is genuinely useful routing language. However there is no when-not guidance, no mention of when to prefer search_get_metrics or analytics tools instead, and no prerequisites such as whether a location must already be connected.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.