Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

wallapop_search

Search public Wallapop listings by query and coordinates, with filters for category, price, condition, distance, shipping, and sort order; returns paginated listing cards with item URLs.

Instructions

Search Wallapop public listings. Returns one page of public Wallapop listing cards with title, price, currency, images, coarse location, taxonomy, shipping state, and a public item URL. q is a free-text search. latitude and longitude are required caller-provided coordinates because Wallapop otherwise infers location from the server's network location. category_id accepts any ID returned by /wallapop/categories, including descendants. sort is one of closest, most_relevance, newest, price_low_to_high, or price_high_to_low. When category_id is supplied, discover condition values from /wallapop/filters; categories can add values beyond the base set. Use /wallapop/filter-options for remote filter values. Pass next_cursor back as cursor by itself to fetch the next page.

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": {
      "q": "<q>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "wallapop_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFree-text listing search, 2 to 200 characters
sortNoWallapop sort order
cursorNoOpaque next_cursor returned by a previous response. Use it alone, without initial search parameters.
filterNoRepeatable category-specific key:value pair discovered from /wallapop/filters, e.g. brand:BMW, color:Black, has_warranty:true, storage_capacity:128gb, item_language:english, or fashion_size:3,4. For remote values use IDs returned by /wallapop/filter-options.
latitudeYesCaller-provided search latitude, -90 through 90
conditionNoRepeatable or comma-separated condition values. With category_id, use the current values from /wallapop/filters; without category_id, base values are new, as_good_as_new, good, fair, and has_given_it_all.
longitudeYesCaller-provided search longitude, -180 through 180
max_priceNoMaximum sale price
min_priceNoMinimum sale price
category_idNoAny live search taxonomy ID from /wallapop/categories
time_filterNoListing date window
is_shippableNoPass true to limit to shipping-capable listings; omit to include all. false is rejected because Wallapop ignores it.
distance_in_kmNoMaximum distance from the supplied coordinates, 0 through 1000 km

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well. It discloses the one-page return format, the fields returned, the location-inference quirk requiring caller-provided coordinates, category descendant behavior, condition-value discovery, remote filter values, and cursor-only pagination.

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 front-loaded with purpose and return shape, then moves through the key parameter quirks and pagination. Despite its length for a 13-parameter tool, every sentence carries operational value.

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?

For a 13-parameter search tool with no output schema and no annotations, the description is complete enough to call correctly. It covers return contents, location requirements, category and filter discovery, sorting, condition handling, and cursor pagination.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines all parameters. The description still adds meaningful semantics: why latitude/longitude are required, that category_id may include descendants, that condition values can vary by category, where to discover filter values, and how cursor must be used alone.

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 states a specific verb and resource: search Wallapop public listings. It also specifies the return shape as one page of listing cards containing title, price, images, location, taxonomy, shipping state, and item URL, which clearly distinguishes it from detail/category/filter sibling tools.

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

Usage Guidelines4/5

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

It gives clear operational guidance: latitude/longitude are required because Wallapop otherwise infers server location, category_id should come from /wallapop/categories, and condition/filter discovery should use /wallapop/filters and /wallapop/filter-options. It also explains cursor-only pagination. It stops short of explicitly naming when to use wallapop_item_detail instead, so it is strong but not fully exhaustive.

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