Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

wallapop_item_detail

Fetch a public Wallapop listing detail page from a clean item URL and return parsed description, price, condition, images, location, shipping, attributes, and related links.

Instructions

Fetch a public Wallapop listing detail page. Returns public listing details parsed from the anonymous server-rendered item page: description, price, taxonomy, condition, images, coarse location, shipping, category attributes, hashtags, and related-search links. Pass a clean https item URL returned by /wallapop/search, using es.wallapop.com, it.wallapop.com, or pt.wallapop.com. Seller/profile/contact data, exact coordinates, postal codes, favorites, and view-tracking state are omitted. The upstream may rate-limit or block requests; this endpoint retries automatically (up to three attempts).

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": {
      "url": "<url>"
    },
    "name": "wallapop_item_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesClean https public item URL from /wallapop/search on es.wallapop.com, it.wallapop.com, or pt.wallapop.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/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 behavioral burden and does so well: it discloses that data comes from an anonymous server-rendered page, lists omitted fields (seller/profile/contact, exact coordinates, postal codes, favorites, view-tracking), and warns about upstream rate-limiting/blocking with automatic retries up to three attempts.

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?

Front-loads purpose and return contents, then usage constraints, omissions, and reliability behavior. Every sentence adds actionable information with no filler.

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 no-annotation, no-output-schema, single-parameter detail tool, the description covers what is returned, what is deliberately omitted, how to obtain the URL, and upstream reliability behavior. Nothing essential for correct invocation is missing.

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

Parameters3/5

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

The single URL parameter is fully described in the schema, so the baseline is 3. The description reinforces the domain restriction and search-origin requirement but adds no syntax or format detail beyond what the schema already provides.

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?

States a specific verb and resource: 'Fetch a public Wallapop listing detail page.' It also enumerates the returned data and distinguishes itself from the search flow by requiring a URL 'returned by /wallapop/search,' so an agent can identify it without opening the schema.

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?

Clearly says to pass a clean https item URL from /wallapop/search and restricts domains to es/it/pt.wallapop.com. It does not explicitly state when not to use this tool, but the prerequisite is strong enough to route an agent correctly.

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