Skip to main content

What it does

The Get Business Reviews tool fetches Google reviews for a business or place. It accepts a place_id directly (from Search Google Maps) for maximum reliability, or falls back to an internal Google Maps search using business_name (+ optional location) to resolve the place first. Great for reputation research, sentiment summaries, competitor review analysis, and lead-gen quality signals.

Key features

  • Works with a known place_id or a business name
  • Auto-lookup fallback — no need to pre-run a maps search if you only have a name
  • Sort reviews by relevance, newest, highest rating, or lowest rating
  • Pagination via next_page_token for fetching additional pages
  • Optional topic filtering via Google topic_id

Parameters

Either place_id or business_name is required. Passing place_id is strongly preferred — auto-lookup by name uses Google’s top search result, which can be ambiguous for common names.

Common use cases

Fetch reviews by place_id (preferred)

Fetch reviews by business name (auto-lookup)

The tool first resolves the place_id via Google Maps, then returns reviews. The response includes resolved_via: "name_lookup" so you know the fallback was used.

Paginate through more reviews

Get the worst reviews (risk research)

What you get back

Best practices

  • Always prefer place_id over business_name when you have it — faster and disambiguated
  • Pair with Search Google Maps at the start of a workflow to capture place_ids for batch processing
  • Use sort_by: "newest" for fresh signals (recent service quality, new menu, etc.) and sort_by: "lowest_rating" for risk/complaint analysis
  • Paginate only as needed — 10 reviews is usually enough for a summary

Troubleshooting

“Could not find a Google Maps place for <name>”
  • Add a location (city, state) to disambiguate
  • Fall back to calling search_google_maps directly and passing the place_id explicitly
“Either place_id or business_name is required”
  • You called the tool with neither — pass one of them
Fewer reviews than expected
  • Use next_page_token to paginate
  • Try a different sort_by — each sort surfaces a different slice