Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wallapop_item_detail

Read-only

Fetch the public detail page for one Wallapop listing using its item URL from wallapop_search. Returns listing text, price, condition, category attributes, images, coarse location, shipping, hashtags, and related searches. Seller/profile/contact data, exact location, favorites, and tracking state are omitted. Retries up to three times; upstream access remains intermittent.

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
urlYesRequired public item URL from wallapop_search. Accepts https://es.wallapop.com/item/{slug}, https://it.wallapop.com/item/{slug}, or https://pt.wallapop.com/item/{slug}.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the exact field set returned, the fields deliberately omitted (seller/profile/contact, exact location, favorites, tracking state), and the retry-and-instability behavior. That omission list and the flakiness warning are precisely the operational context an agent needs to plan around failures.

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 tight sentences, front-loaded with the action and scope, then returns, exclusions, and reliability. The field enumeration mildly overlaps the output schema, but the remaining sentences earn their space.

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?

An output schema exists, so the description needn't fully specify the return shape, yet it summarizes it anyway and adds the exclusion list plus the intermittent-upstream caveat. For a single-parameter read tool with annotations, nothing an agent needs 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?

With one required parameter and 100% schema description coverage, the schema already documents the URL and the accepted es/it/pt hosts. The description only adds provenance ('from wallapop_search'), so the baseline of 3 applies rather than a higher score.

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 the public detail page for one Wallapop listing') and anchors the input to 'its item URL from wallapop_search', which cleanly separates it from the search sibling. There is no ambiguity about what the tool retrieves.

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?

The phrase 'using its item URL from wallapop_search' establishes the intended two-step workflow (search first, then detail) and implicitly rules out using this without a prior search result. There is no explicit statement of when NOT to use it, but the context is clear enough for correct selection.

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

All Crawlora MCP toolsInspect
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.

Resources