Get Google Maps place reviews
Input
count optionalHow many reviews to return at most. Places with few reviews return fewer.
Default: 12placeId optionalThe Google place id, as google.com/search_places returns it. A place id Google does not know fails with a clear error.
placeUrl optionalThe place's Google Maps link, as google.com/get_place returns it in resolvedUrl. The most reliable input; used instead of placeId when both are given.
Output
n optionalNumber of reviews returned. 0 when the place has no reviews at all.
reviews optionallimitedView optionalTrue when fewer reviews than asked came back because Google showed this browser its limited view, which stops the list after the first reviews until the browser is signed in to Google. False when the count was reached or the place has no more reviews.
FAQ
Search Google
Run a Google search and return the page's organic result cards (title, url, site, byline, meta, snippet), with redirect wrappers already cleaned from urls. Runs logged out by default; if the browser happens to carry Google cookies, results are personalized to that account/IP. Google serves result links as redirects rather than destination addresses, so each one is followed far enough to read the address it points at before the results are returned. That adds a fraction of a second per result, and each destination site sees one request. Supports full Google query syntax: site:, quoted "exact phrases", OR, -exclude, intitle:. Quoted phrases return a smaller, more precise set; dropping quotes broadens recall with some near-miss results mixed in. Use site: to scope a domain/path, e.g. site:www.linkedin.com/in. Each call returns one results page (up to ~10 organic cards, no per-call count option). Use `page` (0-based) to move through further pages, mirroring the search results pager. Pages are reproducible on the same account/IP and are largely non-overlapping (occasional overlap of one result at page boundaries), so different pages can be fetched concurrently and unioned — always dedupe by canonical url. Narrow queries return the same results in the same order across replays on one account/IP; very broad, high-volume queries may reorder between runs. For broader coverage, fetch multiple pages concurrently and/or split the query itself — vary the site: path, phrases/OR-terms, or use `freshness` for disjoint date-bounded windows. Always dedupe by url.
Search Google Maps places
Search Google Maps for places, optionally near a location, and get the list Maps shows, in its order: name, address, phone, website, main category and all categories, star rating, number of reviews, price range, coordinates and the Google place id. Use the place id with get_place for the opening hours and with get_place_reviews for the reviews. Google Maps lists at most 120 places for one search; complete is true when that list ended, false when cap stopped it first. A precise query that Maps opens as one place returns that one place. Category names follow hl, or the browser's language when hl is empty.
Search Gmail
Search the signed-in Gmail with the native query syntax (from:, to:, subject:, has:attachment, after:/before:, labels…) and return matching threads: threadId (feed it to get_thread / reply_to_email), sender, senderEmail, subject, snippet, date, unread, starred, hasAttachment. Results are threads rather than individual messages, which is Gmail's own search granularity, and only the first page of results is returned (up to 50).