get_venues — Get details for several venues
Full details (same fields as get_venue) for up to 50 venues or places in one call, e.g. every stop of an itinerary. Pass ids and/or slugs from previous results; duplicates are fetched once. Results keep the order you passed (ids first, then slugs); anything not found is listed in not_found instead of failing the call.
Required arguments: None at JSON Schema level. Tool annotations: readOnlyHint: true, openWorldHint: true.
Input parameters
| Field | Type | Required | Description and allowed values |
|---|---|---|---|
ids |
array<string> |
No | Node IDs from other tools' results. Up to 50 items |
slugs |
array<string> |
No | Evendo slug paths, if you have them instead of IDs. Up to 50 items |
Example arguments
{
"ids": ["3127593"],
"slugs": ["united-kingdom/london"]
}Exact JSON Schema
The full input schema is in schemas/mcp-tools-snapshot.json (the live tools/list response, captured 10 November 2026), and this page is generated from it. Additional properties are rejected (additionalProperties: false).
Practical requirement: Pass at least one of ids or slugs (up to 50 each). Each result has the same fields as get_venue, including place_score. Results keep the order you passed; anything not found is listed in not_found instead of failing the call. Use this instead of many get_venue calls, for example to fetch every stop of an itinerary.