google-maps__search_along_route
Call this tool when the user wants to find places, businesses, or points of interest along a travel route (e.g., "gas stations on my way to Tahoe", "coffee shops between SF and San Jose"). Calling this tool incurs higher cost than search_places, so use search_places instead when searching near a single location rather than along a route.
Input Requirements (CRITICAL):
text_query(string - MANDATORY): A natural language description of what to search for along the route. *
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": {
"textQuery": "<textQuery>"
},
"name": "google-maps__search_along_route"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| textQuery | Yes | Required. Natural language search query (e.g., "ev chargers", "coffee"). | |
| regionCode | No | Optional. Country/region code (CLDR) of location (e.g., "US"). | |
| travelMode | No | Optional. Specifies the travel mode used to compute the route and the detours. Defaults to `DRIVE`. `WALK` and `BICYCLE` are only supported with `route_endpoints`. `TRANSIT` is not supported. | |
| languageCode | No | Optional. The language for summary and place details. Defaults to "en-US". | |
| retrievalToken | No | A retrieval token returned from a prior ComputeRoutes call representing the route. Only one of the following fields should be set: this field, encodedPolyline, routeEndpoints. | |
| routeEndpoints | No | Explicit route endpoints (origin and destination). Only one of the following fields should be set: this field, encodedPolyline, retrievalToken. | |
| encodedPolyline | No | An encoded polyline string representing the route. See https://developers.google.com/maps/documentation/utilities/polylinealgorithm. Only one of the following fields should be set: this field, retrievalToken, routeEndpoints. | |
| routingPreference | No | Optional. Optional routing preference specifying how traffic data is used. Defaults to TRAFFIC_UNAWARE. | |
| includeExtendedDetails | No | Optional. Includes extended place details in the response. Set this field to `true` when the user request requires rich qualitative insights, real-time dynamics, or specialized entity attributes: - Qualitative reviews, customer sentiment, and feedback. - Specific offerings like menu items, dishes, food specialties, beverages, or business highlights. - Qualitative atmosphere, interior decor, aesthetic, ambience, or mood. - Real-time data and specialized facility specs, visitor policies/tips, wait times. Leave `false` (default) for standard discovery searches (e.g., cuisines, store types), location/address lookups, contact info, operating hours, and standard metadata/amenities. Enabling this field may incur higher latency. |