Skip to main content
Glama

ReviewTactic — Google Review Checker

Check local search rank on Google Maps

check_local_rank
Read-only

Checks where a business appears in Google Maps results for one search phrase, searched from one point (latitude and longitude). Returns its rank, the number of results seen, and up to 5 competitors ranked above it with their ratings and review counts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>",
      "business_name": "<business_name>",
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "check_local_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude of the point to search from.
lngYesLongitude of the point to search from.
keywordYesThe search a customer would type, e.g. "pizza near me".
business_nameYesBusiness name as it appears on Google.

Output Schema

NameRequiredDescriptionDefault
rankNo
totalNo
statusYes
messageNo
learn_moreNo
matched_nameNo
competitors_aboveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context that results are point-specific and mentions the shape of the response, but it omits what happens when the business is not found in results, whether calls are metered or rate-limited, and how fresh the Google Maps data is.

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?

Two sentences, front-loaded with the core action and scoped by the second clause about a single phrase and point. Every clause carries information; nothing is redundant or padded.

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?

With an output schema present and full parameter coverage, the description carries only the burden of framing the call, which it does. The main gap is the absence of guidance on the not-found / no-rank outcome and on batching multiple points or keywords.

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 coverage is 100% and each parameter is well described in the schema, including that lat/lng describe the point searched from. The description restates the single-point constraint but adds no syntax, format, or validation meaning beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb and resource ('checks where a business appears in Google Maps results') plus an explicit scope: one search phrase from one lat/lng point. No sibling covers rank checking, so the agent can identify this tool's job immediately from the description alone.

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?

Usage is implied by the stated scope ('one search phrase, searched from one point'), suggesting repeated calls for multiple keywords or locations, but the description never says when to choose this tool over others or when not to use it. No alternatives or prerequisites are named.

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.