Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

wolt_search

Search Wolt restaurants and stores by coordinates, keyword, or category, and verify if delivery is available.

Instructions

Search Wolt restaurants and stores near a coordinate. Returns restaurants and stores near a coordinate, optionally filtered by a keyword or browsed by category. With none of those, this reads Wolt's own plain location browse; with a query it uses Wolt's own keyword search across restaurant/store names, dishes, and cuisines; with a category it browses Wolt's own per-category listing (the same page a homepage cuisine tile links to) -- call /wolt/search/filters for the current, complete, location-scoped list of valid category values. category and query cannot be combined. A keyword search additionally accepts sort, product_line, and open_now; those three apply to keyword search only and return a 400 without query. Each result carries its slug (the value the restaurant and menu endpoints take), name, address, coordinates, tags, price range, rating, and delivery estimate; the two browse modes additionally carry each venue's own category ids. The response also carries is_serviceable, which says whether Wolt delivers to the requested coordinates at all: false means the coordinates are outside Wolt's delivery coverage, so the empty results list is a coverage answer rather than a no-matches answer. A keyword that simply matches nothing inside a covered area returns an empty list with is_serviceable true. Call /wolt/cities for the coordinates of every city Wolt operates in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOptional result ordering. Only applies together with query -- Wolt exposes sorting on its keyword search only, not on its plain browse or category listings.
limitNoMax restaurants/stores returned. Defaults to 30, maximum 100.
queryNoOptional keyword to search restaurant/store names, dishes, or cuisines by. Cannot be combined with category.
categoryNoOptional Wolt category id to browse by instead of a keyword search, e.g. pizza, sushi, vegan. Call /wolt/search/filters for the current, complete, location-scoped list of valid values. Cannot be combined with query. A value Wolt does not recognize at all returns a 404; a real category this particular market does not use returns an empty list, since the taxonomy is location-scoped and markets differ.
latitudeYesSearch center latitude
open_nowNoWhen true, restrict results to venues currently delivering. Only applies together with query.
longitudeYesSearch center longitude
product_lineNoOptional store-type filter. Only applies together with query. Which store types a market actually stocks varies by country; one absent from the searched market returns no results rather than an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / product_line / enum
      Added value: +[
      +  "restaurant",
      +  "grocery",
      +  "alcohol",
      +  "pharmacy",
      +  "pet_supply",
      +  "health_and_beauty",
      +  "electronics",
      +  "toys_games_and_kids",
      +  "home_and_diy",
      +  "florist",
      +  "general_merchandise",
      +  "gift_card",
      +  "charity",
      +  "subscription",
      +  "other"
      +]
    • addedInput schema / properties / sort / enum
      Added value: +[
      +  "recommended",
      +  "distance",
      +  "rating",
      +  "delivery_fee",
      +  "delivery_estimate"
      +]
  2. Addedv1.16.2

TDQS

A5/5.0
Behavior5/5

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

Since no annotations exist, the description carries the full burden, and it excels: it explains the is_serviceable field, the meaning of empty results, error codes (400, 404), and the difference between unrecognized vs unused categories. It also details the result fields and extra category ids for browse modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence adds value: purpose, modes, constraints, response details, and auxiliary calls. It is logically ordered and front-loads the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description covers all necessary response aspects (fields, is_serviceable, errors) and points to related tools for additional data. It is comprehensive for an 8-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description adds interaction semantics: category vs query exclusivity, conditional application of sort/product_line/open_now, and the specific meaning of category errors. It also explains the source of valid category values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches Wolt restaurants and stores near a coordinate, and distinguishes three modes (plain browse, keyword search, category browse). It names specific sibling tools like /wolt/search/filters and /wolt/cities, making its role unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly explains when to use each mode, the constraints (category and query cannot combine), and that sort/product_line/open_now only work with query. It also directs to wolt_search_filters for valid categories and wolt_cities for coordinates, providing clear alternatives.

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

Deploy Server

Other Tools