get_menu
The menu, read from the restaurant's own website: sections and items with prices as
printed. Menus that are only images or scanned PDFs come back as attached images for you
to read; a result holds a few, and says how to get the rest. Typically 5-90 s the first
time (slow sites can take longer), then served from cache for the configured lifetime. website_status explains an empty result
(no_menu_found, blocked, robots_disallowed, unreachable...).
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_menu"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| website | No | The restaurant's website, when you have it and no place_id. | |
| place_id | No | place_id from find_restaurant or search_restaurants. | |
| media_offset | No | Index of the first menu image to attach. A result that could not attach every image says which offset to ask for next. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| skipped | Yes | ||
| sources | Yes | ||
| website | Yes | ||
| renderer | No | ||
| final_url | No | ||
| fetched_at | No | ||
| fetch_count | No | ||
| render_calls | No | ||
| website_status | No | ok |