Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wallapop_item_detail

Fetch parsed public Wallapop listing details from a clean item URL to retrieve price, description, condition, images, shipping, coarse location, attributes, and related searches.

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 uses the measured browser_android_native@fresh profile and retries up to three times.

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.6/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so: it discloses what is deliberately omitted (seller/profile/contact data, exact coordinates, postal codes, favorites, view-tracking state), warns about upstream rate-limiting/blocking, and names the fetch profile plus a three-retry policy. That is exactly the behavioral context an agent needs before committing a call.

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?

Four sentences, front-loaded with the purpose and return contents, then input rules, then omissions and reliability caveats. Dense but each sentence carries distinct information; the domain list and omission list are slightly list-heavy but not padded.

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 single-parameter scrape endpoint with no annotations and no output schema, the description supplies the return-field inventory, the exclusion list, input constraints, and failure-mode behavior. Nothing an agent needs to call this correctly or interpret the result 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% and the single url parameter is already documented in the schema, so the baseline is 3. The description adds real meaning beyond it by specifying URL provenance (/wallapop/search), the "clean" form, and the three accepted hostnames, which constrains input format in a way the schema does not spell out.

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") and immediately enumerates the returned fields. It also distinguishes itself from the sibling wallapop_search by requiring a URL that comes from that search endpoint, so an agent can route between the two without inspecting schemas.

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?

Explicit precondition: pass a clean https item URL returned by /wallapop/search, restricted to es/it/pt.wallapop.com subdomains. That tells the agent when this tool applies and what input is valid, but there is no explicit statement of when NOT to use it (e.g. use wallapop_search when you only have a query, not a URL).

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