goplaces MCP

Overview Schema Source Related Servers Discussions Admin

Search places

goplaces_search

Read-onlyIdempotent

Search Google Places by free-form text to find businesses, landmarks, restaurants, shops, or services. Filter by open now, rating, price, type, and location, then return compact place summaries.

Instructions

Search Google Places by free-form text. Use for finding businesses, landmarks, venues, restaurants, shops, attractions, or services. Supports filters for open now, rating, price, type, pagination, and optional circular location bias. Returns compact place summaries and a next_page_token when Google provides one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	No	Latitude for a circular location bias/restriction.
`lng`	No	Longitude for a circular location bias/restriction.
`limit`	No	Maximum number of results.
`query`	Yes	Search text, e.g. 'coffee', 'sushi near Bryant Park', or 'EV charging'.
`region`	No	Optional CLDR region code, for example 'US' or 'DE'.
`keyword`	No	Extra keyword appended to the text query.
`language`	No	Optional BCP-47 language code, for example 'en' or 'en-US'.
`open_now`	No	When true, request places currently open.
`radius_m`	No	Radius in meters for the circular location bias/restriction.
`include_ev`	No	Include EV charging connectors, charge rates, and availability.
`min_rating`	No	Minimum star rating from 0 to 5.
`origin_lat`	No	Latitude to measure travel from. With origin_lng, each result gains distance_meters and duration_seconds, avoiding a directions call per result.
`origin_lng`	No	Longitude to measure travel from. Must be paired with origin_lat.
`page_token`	No	Google next_page_token from a previous goplaces_search response. Every other argument, detail_level included, must match the original request or Google rejects the page.
`origin_mode`	No	Travel mode for origin distances. Google does not support transit here.	drive
`detail_level`	No	Field tier to request. Google bills at the most expensive tier in the request, so prefer the cheapest that answers the question: 'ids' returns place IDs only, 'basic' adds name, address, location, type, and a Maps link, and 'full' adds rating, price, hours, phone, and website.	full
`price_levels`	No	Google price levels: 0 free, 1 inexpensive, 2 moderate, 3 expensive, 4 very expensive.
`included_type`	No	Optional Google place type filter, e.g. 'restaurant', 'cafe', 'park'.
`ev_connector_types`	No	Keep only places supporting one of these Google connector types, e.g. ['EV_CONNECTOR_TYPE_CCS_COMBO_2', 'EV_CONNECTOR_TYPE_NACS', 'EV_CONNECTOR_TYPE_J1772', 'EV_CONNECTOR_TYPE_TESLA', 'EV_CONNECTOR_TYPE_CHADEMO', 'EV_CONNECTOR_TYPE_TYPE_2'].
`include_atmosphere`	No	Include the most expensive tier: editorial summary, dine-in/takeout/delivery/reservable, accessibility, and parking options.
`ev_min_charge_rate_kw`	No	Keep only charging stations at or above this rate in kilowatts.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only on failure; the result is also flagged isError.
`results`	No	Matching places, best match first.
`next_page_token`	No	Pass back as page_token for the next page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: it returns compact summaries and a next_page_token, and it advertises pagination and location-bias support. It does not, however, mention billing tier implications or pagination constraints (those live in the schema).

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?

Three sentences, front-loaded with the action and scope, then filters, then return shape. The mid-sentence enumeration of place categories is somewhat listy but earns its place by clarifying the query domain.

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?

For a 21-parameter tool with an output schema, the description need not explain return values, and it correctly defers detail to the schema. It covers scope, filters, and pagination. The only omission is routing versus siblings like goplaces_nearby.

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 all 21 parameters are already documented in the schema. The description only lists filter categories (open now, rating, price, type, pagination, location bias), which echoes but does not add meaning beyond the structured field docs. Baseline 3 applies.

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?

States a specific verb and resource ('Search Google Places by free-form text') plus the scope of things it can find. However, it never names the sibling tools it overlaps with (goplaces_nearby for proximity, goplaces_autocomplete for prefix matching), so the agent must infer the boundary from other tools' descriptions.

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?

The 'Use for finding businesses, landmarks, venues, restaurants, shops, attractions, or services' sentence gives clear task context. It does not state when-not to use it or point to an alternative sibling, which is the main gap.

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

Deploy Server