Skip to main content
Glama

Visibility Genies

Get business reviews

get_business_reviews

Collects the Google reviews of one business, with rating, author, date, text and the owner's reply, for review-gap analysis. Name the business with exactly one of businessName, cid or placeId (cid is the most precise). Usually completes within this call; if the queued job is still running you get status 'processing' plus a taskId, so call again with that taskId in 30-60 seconds to collect it at no extra cost. Estimated price: $0.01 for 20 reviews, billed per 10 (per 20 with includeOtherSources) at twice the Local page's normal-priority rate, so the call usually returns them; reviews bought within a day, here or on the Local page, are answered at no charge. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_business_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidNoGoogle-defined business CID (from get_local_serp_results rows). Most precise identifier.
nearNoCoordinate to search from. Use it when the business name is ambiguous; otherwise locationCode is enough.
depthNoNumber of reviews to collect (10-200). Defaults to 20. Billed per 10 reviews, per 20 with includeOtherSources.
sortByNoReview order. Defaults to newest. Ignored with includeOtherSources.
taskIdNoResume a previous call that returned status "processing". Pass the taskId back exactly as returned ("google:<id>" or "extended:<id>"). Resuming charges no extra credits.
placeIdNoGoogle Maps place_id (from get_local_serp_results rows).
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
businessNameNoBusiness name as it appears on Google. Supply exactly one of businessName, cid, or placeId.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoLocation code. Ignored when `near` is set; otherwise defaults to the project's market.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.
includeOtherSourcesNoAlso collect the reviews Google shows from Yelp, Tripadvisor and Trustpilot. Costs more and cannot be sorted.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
statusYes
taskIdYes
totalsNo
reviewsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Far beyond the annotations, which only say readOnlyHint=false and openWorldHint=true. The description discloses the async job model ('processing' plus taskId), the pricing model and per-10/per-20 billing, free reuse of recently purchased reviews, the workspace spend limit, and the exact refusal-then-approve recovery path. This is exactly the behavioral context an agent needs for a paid, non-destructive job.

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?

Front-loaded with purpose and identifier rules, which is good, but the single dense paragraph crams in repetitive pricing clauses ('billed per 10 (per 20 with includeOtherSources) at twice the Local page's normal-priority rate, so the call usually returns them') that are hard to parse and partly restate the depth parameter's schema text.

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?

For a 12-parameter, nested-object, paid, asynchronous tool with an output schema, the description covers identifiers, cost, spend-limit refusal, resumption, and what the response looks like when still processing. Nothing an agent needs to call it correctly or recover from failure is missing.

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 baseline is 3, but the description adds real meaning: the exactly-one-of rule among the three business identifiers, cid's precision ranking, and how depth/includeOtherSources drive cost. It does not explain languageCode or locationCode interactions beyond what the schema already states.

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?

Specific verb and resource ('Collects the Google reviews of one business') plus the returned fields (rating, author, date, text, owner reply) and a stated use case (review-gap analysis). Naming Google explicitly differentiates it from the TripAdvisor and Trustpilot review siblings without needing their schemas.

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?

Gives concrete routing rules: pick exactly one of businessName/cid/placeId, prefer cid, resume a queued job with taskId after 30-60 seconds, and ask the user before setting approvedMaxCostUsd. It stops short of stating when to prefer a different review source (TripAdvisor/Trustpilot), which is left to inference.

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.

Resources