DevelopersRead only

list_menu_items

API reference — one of six tools an AI assistant can call on an Avrosh account.

What it does

Every item on this business's menu or product list - category, name, description, price, availability, dietary and allergen tags, photos. This is the management view: complete and uncapped, unlike what the AI reads out on a call. Call it before ANY menu write so you edit a real id and quote the stored price, not one you remember. Prices are whole numbers in the business's own currency.

This is the exact text the model reads before deciding to call.

Parameters

business_idstringrequired

The id returned by list_businesses.

Request

curl -X POST https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_menu_items","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87"}}}'

Response

The result arrives as an MCP content block; the JSON below is what the text field parses to.

{
  "items": [
    {
      "id": "a41c…",
      "category": "food",
      "name": "Nasi goreng spesial",
      "priceIdr": 45000,
      "available": true,
      "dietary": [],
      "allergens": [
        "egg"
      ],
      "photoUrl": "/uploads/…"
    }
  ],
  "count": 1
}

Authentication

Every request carries Authorization: Bearer avk_…. Create a key in the Avrosh dashboard under Docs; it is shown once, because only its hash is stored.

One key reaches every business on the account that made it, and no others. There are no scopes to configure and nothing to switch on — a connected assistant receives the whole toolset. What bounds it is whose account the key belongs to, which is enforced in the database rather than by a permission anybody sets.

curl https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY"