Skip to main content
Glama
Sign In
ScrapeBadger MCP Server

ScrapeBadger MCP Server

Official
by scrape-badger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

autoscout24_get_listing

Retrieve complete AutoScout24 vehicle listing details—specifications, equipment, photos, price, and seller data—by supplying a listing URL or ID.

Instructions

Get full AutoScout24 listing detail: native specifications, equipment, photos, prices and public seller data. Supply exactly one url or listing_id from vehicle search; the URL decides the market, otherwise de. 10 credits; removed or missing listings are unbilled 404s. Swiss listings are unsupported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "autoscout24_get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoFull HTTPS listing URL from vehicle search results. Supply url or listing_id, not both.
marketNoInferred from url, otherwise de. An explicit market must match the URL host.
listing_idNoListing UUID from search results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does so well: it discloses the 10-credit cost, that removed/missing listings return unbilled 404s, and that market resolution comes from the URL host. It stops short of describing rate limits, retry behavior, or how the market mismatch case is reported.

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?

Four short sentences, each carrying distinct information: what you get, how to invoke it, how market is resolved, and cost/error behavior. The most decisive facts (exactly one input, 10 credits, unsupported market) are placed where an agent will see them before acting.

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?

No output schema exists, and the description compensates by enumerating the returned fields and confirming seller data is public. Cost, failure semantics, market resolution, and the unsupported-market case are all covered, leaving nothing material an agent needs in order to call this correctly.

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?

Schema coverage is 100%, so the three parameters are already documented, including the url-or-listing_id exclusivity and the market inference rule. The description restates those same constraints rather than adding new meaning, so this sits at the baseline 3 for a fully documented schema.

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?

"Get full AutoScout24 listing detail" pairs a specific verb with a specific resource, then enumerates the payload (specifications, equipment, photos, prices, public seller data) so an agent knows exactly what comes back. The scope constraint (Swiss listings unsupported) further sharpens what the tool does and does not cover.

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 states the precondition clearly: supply exactly one url or listing_id taken from vehicle search, and notes the URL determines the market with de as the fallback. It also gives an explicit exclusion (Swiss listings unsupported). It does not name a concrete alternative tool by name, which keeps it just short of a 5.

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