Crawlora MCP

wallapop_search

Read-only

Search Wallapop's anonymous public listings in a caller-selected area. Returns normalized listing cards (title, price, images, coarse location, category, shipping) and an opaque next_cursor. Supply latitude and longitude; use wallapop_categories for valid category IDs and wallapop_filters plus wallapop_filter_options for live filter values and category-specific condition values. Dynamic examples include has_warranty:true, storage_capacity:128gb, and multi-select fashion_size:3,4. Pass next_cursor alone to continue a search.

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>"
    },
    "name": "wallapop_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Required for a new search; 2 to 200 characters. Omit when continuing with cursor.
`sort`	No	Optional. One of closest, most_relevance, newest, price_low_to_high, price_high_to_low. Defaults to most_relevance.
`cursor`	No	Opaque next_cursor from a prior search response. Pass it alone to continue.
`filter`	No	Optional repeatable key:value pair from wallapop_filters. Local values such as storage_capacity:128gb and toggles such as has_warranty:true are validated from the selected category's live schema; use wallapop_filter_options for remote option IDs.
`latitude`	No	Required for a new search. Caller-provided latitude from -90 through 90; omit with cursor.
`condition`	No	Optional repeatable or comma-separated condition values. With category_id, use the live condition options from wallapop_filters; without a category, base values are new, as_good_as_new, good, fair, and has_given_it_all.
`longitude`	No	Required for a new search. Caller-provided longitude from -180 through 180; omit with cursor.
`max_price`	No	Optional maximum sale price.
`min_price`	No	Optional minimum sale price.
`category_id`	No	Optional live category ID from wallapop_categories; parent and descendant IDs are accepted.
`time_filter`	No	Optional listing date: today, lastWeek, or lastMonth.
`is_shippable`	No	Optional. Pass true to limit to shipping-capable listings; omit to include all. false is rejected because the upstream ignores it.
`distance_in_km`	No	Optional radius from the supplied coordinates, 0 through 1000 km.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / condition / description

Previous value: -"Optional repeatable or comma-separated values: new, as_good_as_new, good, fair, has_given_it_all."New value: +"Optional repeatable or comma-separated condition values. With category_id, use the live condition options from wallapop_filters; without a category, base values are new, as_good_as_new, good, fair, and has_given_it_all."

changedInput schema / properties / filter / description

Previous value: -"Optional repeatable key:value pair from wallapop_filters; use wallapop_filter_options for current brand/model IDs."New value: +"Optional repeatable key:value pair from wallapop_filters. Local values such as storage_capacity:128gb and toggles such as has_warranty:true are validated from the selected category's live schema; use wallapop_filter_options for remote option IDs."

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds useful context beyond that — the response shape (normalized listing cards with title, price, images, coarse location, category, shipping) and the opaque cursor contract. It does not mention result limits, rate limiting, or total-count behavior, so it is not a full behavioral picture.

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

Conciseness4/5

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

Five sentences, front-loaded with purpose and return shape before the prerequisite and filter guidance; no filler. The middle sentence listing helper tools is somewhat run-on, which keeps it from being maximally scannable.

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 open-world search with an output schema already present, the description covers purpose, prerequisites, discovery of valid category/filter values, cursor continuation, and return shape. Nothing an agent needs to invoke it correctly is missing.

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 baseline would be 3; the description nevertheless adds cross-parameter meaning by explaining that latitude/longitude are required for a new search and that next_cursor is passed alone, plus real dynamic filter examples (has_warranty:true, storage_capacity:128gb, multi-select fashion_size:3,4) that show the key:value form. Some of this overlaps the schema text, keeping it below a 5.

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?

Specific verb+resource+scope: 'Search Wallapop's anonymous public listings in a caller-selected area', which immediately tells an agent this is a geographic marketplace search rather than a lookup. It also names the sibling helpers (wallapop_categories, wallapop_filters, wallapop_filter_options) that support it, so the tool's role is unambiguous.

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?

Explicitly states the preconditions ('Supply latitude and longitude'), which sibling tools to call first for categories and filter values, and how to paginate ('Pass next_cursor alone to continue a search'). It does not state when to prefer wallapop_item_detail over search, so it stops short of full alternative routing.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.