HasData

google_maps_place: GET /

hasdata_google_maps_place_getPlaceDetails

Read-only

Get Place Details

Fetches full Google Maps place data by placeId with optional domain/language localization. Returns name, address, coordinates, phone, website, categories, hours, rating, review count, price level, photos, attributes/amenities, and plus_code. With fetchWebResults, also returns the place panel's web results (the business's own site and its Instagram, Facebook, delivery and other listings) with title, link, displayed link and snippet. Use for local SEO audits, POI enrichment, lead generation, competitor mapping, and building location-aware agents.

Input Schema

TableJSON Schema

Name	Required	Description
`hl`	No	The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.
`domain`	No	Google domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`.
`placeId`	Yes	A unique identifier for the place. This ID can be obtained from Google Maps search results.
`fetchWebResults`	No	Also collect the place panel's "Web results" section (the business's website and its pages on Instagram, Facebook, delivery services, etc.) and return it as `webResults`. This takes an extra request to Google and costs 5 credits on top of the base. Default is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / fetchWebResults

Added value: +{
+  "description": "Also collect the place panel's \"Web results\" section (the business's website and its pages on Instagram, Facebook, delivery services, etc.) and return it as `webResults`. This takes an extra request to Google and costs 5 credits on top of the base. Default is false.",
+  "type": "boolean"
+}

Changed4 schema fields changedJul 24, 2026

changedInput schema / properties / domain / description

Previous value: -"Google domain to use. Default is google.com."New value: +"Google domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`."

removedInput schema / properties / domain / enum

Removed value: -[
-  "google.ac",
-  "google.ad",
-  "google.ae",
-  "google.al",
-  "google.am",
-  "google.as",
-  "google.at",
-  "google.az",
-  "google.ba",
-  "google.be",
-  "google.bf",
-  "google.bg",
-  "google.bi",
-  "google.bj",
-  "google.bs",
-  "google.bt",
-  "google.by",
-  "google.ca",
-  "google.cd",
-  "google.cf",
-  "google.cg",
-  "google.ch",
-  "google.ci",
-  "google.cl",
-  "google.cm",
-  "google.co.ao",
-  "google.co.bw",
-  "google.co.ck",
-  "google.co.cr",
-  "google.co.id",
-  "google.co.il",
-  "google.co.in",
-  "google.co.jp",
-  "google.co.ke",
-  "google.co.kr",
-  "google.co.ls",
-  "google.co.ma",
-  "google.co.mz",
-  "google.co.nz",
-  "google.co.th",
-  "google.co.tz",
-  "google.co.ug",
-  "google.co.uk",
-  "google.co.uz",
-  "google.co.ve",
-  "google.co.vi",
-  "google.co.za",
-  "google.co.zm",
-  "google.co.zw",
-  "google.com",
-  "google.com.af",
-  "google.com.ag",
-  "google.com.ai",
-  "google.com.ar",
-  "google.com.au",
-  "google.com.bd",
-  "google.com.bh",
-  "google.com.bn",
-  "google.com.bo",
-  "google.com.br",
-  "google.com.bz",
-  "google.com.co",
-  "google.com.cu",
-  "google.com.cy",
-  "google.com.do",
-  "google.com.ec",
-  "google.com.eg",
-  "google.com.et",
-  "google.com.fj",
-  "google.com.gh",
-  "google.com.gi",
-  "google.com.gt",
-  "google.com.hk",
-  "google.com.jm",
-  "google.com.kh",
-  "google.com.kw",
-  "google.com.lb",
-  "google.com.ly",
-  "google.com.mm",
-  "google.com.mt",
-  "google.com.mx",
-  "google.com.my",
-  "google.com.na",
-  "google.com.ng",
-  "google.ng",
-  "google.com.nf",
-  "google.com.ni",
-  "google.com.np",
-  "google.com.om",
-  "google.com.pa",
-  "google.com.pe",
-  "google.com.pg",
-  "google.com.ph",
-  "google.com.pk",
-  "google.com.pr",
-  "google.com.py",
-  "google.com.qa",
-  "google.com.sa",
-  "google.com.sb",
-  "google.com.sg",
-  "google.com.sl",
-  "google.com.sv",
-  "google.com.tj",
-  "google.com.tr",
-  "google.com.tw",
-  "google.com.ua",
-  "google.com.uy",
-  "google.com.vc",
-  "google.com.vn",
-  "google.cat",
-  "google.cn",
-  "google.cv",
-  "google.cz",
-  "google.de",
-  "google.dj",
-  "google.dk",
-  "google.dm",
-  "google.dz",
-  "google.ee",
-  "google.es",
-  "google.fi",
-  "google.fm",
-  "google.fr",
-  "google.ga",
-  "google.ge",
-  "google.gg",
-  "google.gl",
-  "google.gm",
-  "google.gp",
-  "google.gr",
-  "google.gy",
-  "google.hn",
-  "google.hr",
-  "google.ht",
-  "google.hu",
-  "google.ie",
-  "google.im",
-  "google.iq",
-  "google.is",
-  "google.it",
-  "google.je",
-  "google.jo",
-  "google.kg",
-  "google.ki",
-  "google.kz",
-  "google.la",
-  "google.li",
-  "google.lk",
-  "google.lt",
-  "google.lu",
-  "google.lv",
-  "google.md",
-  "google.me",
-  "google.mg",
-  "google.mk",
-  "google.ml",
-  "google.mn",
-  "google.ms",
-  "google.mu",
-  "google.mv",
-  "google.mw",
-  "google.ne",
-  "google.nl",
-  "google.no",
-  "google.nr",
-  "google.nu",
-  "google.pl",
-  "google.pn",
-  "google.ps",
-  "google.pt",
-  "google.ro",
-  "google.rs",
-  "google.ru",
-  "google.rw",
-  "google.sc",
-  "google.se",
-  "google.sh",
-  "google.si",
-  "google.sk",
-  "google.sm",
-  "google.sn",
-  "google.so",
-  "google.sr",
-  "google.st",
-  "google.td",
-  "google.tg",
-  "google.tk",
-  "google.tl",
-  "google.tm",
-  "google.tn",
-  "google.to",
-  "google.tt",
-  "google.vg",
-  "google.vu",
-  "google.ws"
-]

changedInput schema / properties / hl / description

Previous value: -"The two-letter language code for the language you want to use for the search."New value: +"The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`."

removedInput schema / properties / hl / enum

Removed value: -[
-  "af",
-  "ak",
-  "sq",
-  "ws",
-  "am",
-  "ar",
-  "hy",
-  "az",
-  "eu",
-  "be",
-  "bem",
-  "bn",
-  "bh",
-  "xx-bork",
-  "bs",
-  "br",
-  "bg",
-  "bt",
-  "km",
-  "ca",
-  "chr",
-  "ny",
-  "zh-cn",
-  "zh-tw",
-  "zh-hk",
-  "co",
-  "hr",
-  "cs",
-  "da",
-  "nl",
-  "xx-elmer",
-  "en",
-  "eo",
-  "et",
-  "ee",
-  "fo",
-  "tl",
-  "fil",
-  "fi",
-  "fr",
-  "fy",
-  "gaa",
-  "gl",
-  "ka",
-  "de",
-  "el",
-  "kl",
-  "gn",
-  "gu",
-  "xx-hacker",
-  "ht",
-  "ha",
-  "haw",
-  "iw",
-  "he",
-  "hi",
-  "hu",
-  "is",
-  "ig",
-  "id",
-  "ia",
-  "ga",
-  "it",
-  "ja",
-  "jw",
-  "kn",
-  "kk",
-  "rw",
-  "rn",
-  "xx-klingon",
-  "kg",
-  "ko",
-  "kri",
-  "ku",
-  "ckb",
-  "ky",
-  "lo",
-  "la",
-  "lv",
-  "ln",
-  "lt",
-  "loz",
-  "lg",
-  "ach",
-  "mk",
-  "mg",
-  "my",
-  "ml",
-  "mt",
-  "mv",
-  "mi",
-  "mr",
-  "mfe",
-  "mo",
-  "mn",
-  "ms",
-  "sr-me",
-  "ne",
-  "pcm",
-  "nso",
-  "no",
-  "nn",
-  "oc",
-  "or",
-  "om",
-  "ps",
-  "fa",
-  "xx-pirate",
-  "pl",
-  "pt",
-  "pt-br",
-  "pt-pt",
-  "pa",
-  "qu",
-  "ro",
-  "rm",
-  "nyn",
-  "ru",
-  "gd",
-  "sr",
-  "sh",
-  "st",
-  "tn",
-  "crs",
-  "sn",
-  "sd",
-  "si",
-  "sk",
-  "sl",
-  "so",
-  "es",
-  "es-419",
-  "su",
-  "sw",
-  "sv",
-  "tg",
-  "ta",
-  "tt",
-  "te",
-  "th",
-  "ti",
-  "to",
-  "lua",
-  "tum",
-  "tr",
-  "tk",
-  "tw",
-  "ug",
-  "uk",
-  "ur",
-  "uz",
-  "vu",
-  "vi",
-  "cy",
-  "wo",
-  "xh",
-  "yi",
-  "yo",
-  "zu"
-]

First observedApr 28, 2026

TDQS

A3.7/5.0

Behavior4/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 genuine behavioral context beyond that: the return payload composition and the fetchWebResults side effect ('extra request to Google and costs 5 credits on top of the base'), which an agent needs for cost-aware planning.

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

Conciseness4/5

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

Front-loaded with the core action, followed by return contents and the fetchWebResults caveat. The long enumeration of returned fields is informative rather than padded, though it could be trimmed slightly; overall it is efficient and well-ordered.

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?

There is no output schema, and the description compensates by enumerating the returned fields in detail, including the webResults sub-shape, so an agent knows what comes back. Safety is covered by annotations; the only mild gap is that it does not state where placeId originates beyond the schema note.

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 description coverage is 100%, so hl, domain, placeId and fetchWebResults are all documented in the schema itself. The description restates placeId-based lookup and localization and elaborates on what fetchWebResults yields, but adds no syntax or format detail beyond the schema, warranting the baseline 3.

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 opens with a specific verb+resource ('Fetches full Google Maps place data by placeId') and enumerates the returned fields, so the agent knows exactly what it retrieves. It does not explicitly contrast itself with the other *getPlaceDetails siblings (yelp, yellowpages, booking) or with performMapSearch, but the 'Google Maps place' scope is unambiguous from the name and text.

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 offers a list of use cases (local SEO audits, POI enrichment, lead generation, competitor mapping), which implies when it is useful, but gives no explicit when-to-use vs alternatives and no exclusions. It never says to obtain placeId from performMapSearch first or to route review queries to getMapReviews, leaving sibling selection to inference.

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

All HasData tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?