marktplaats-mcp

Overview Schema Source Related Servers Discussions Admin

Analyze prices

analyze_prices

Read-onlyIdempotent

Compute price statistics (min, quartiles, median, max, mean) and find cheapest matches for any search on Marktplaats or 2dehands, excluding outliers and non-relevant ads.

Instructions

Price statistics (min, quartiles, median, max, mean) over the most relevant asking prices for a search, plus the cheapest matches. Free, bidding-only and reserved ads are excluded and outliers beyond 1.5x the interquartile range are trimmed. Most reliable with a subcategory plus attributes (e.g. subcategory 'Mobiele telefoons | Apple iPhone', attributes {'Model': 'iPhone 15', 'Opslagcapaciteit': '128 GB'}) instead of free text, which drags in accessories.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`site`	No	Which marketplace: marktplaats (Netherlands) or 2dehands (Belgium).	marktplaats
`query`	Yes	Free-text search, e.g. 'racefiets' or 'iphone 15'. May be empty if a category is given.
`exclude`	No	Drop listings whose title or description contains any of these words, e.g. ['hoesje', 'defect', 'gezocht'].
`category`	No	Top-level category name (Dutch, e.g. 'Fietsen en Brommers') or numeric id. See list_categories.
`delivery`	No	'shipping' for ads that can be shipped, 'pickup' for collection.
`language`	No	2dehands only: 'nl' for Dutch-language ads, 'fr' for French, 'all' (default).
`postcode`	No	Dutch/Belgian postal code to search around, e.g. '1011 AB' or '2000'. Required for distance filtering and for distance_km in results.
`price_to`	No	Maximum price in euros.
`condition`	No	Filter by item condition.
`attributes`	No	Category-specific filters as {filter: value}, using the labels from list_category_filters, e.g. {'Merk': 'Gazelle', 'Framehoogte': '57 tot 61 cm'} or {'Bouwjaar': '2018-2022', 'Kilometerstand': '-100000', 'Brandstof': 'Benzine'}. A list means any of those values. Ranges are 'min-max', 'min-' or '-max'.
`price_from`	No	Minimum price in euros.
`distance_km`	No	Max distance from postcode in kilometers (needs postcode).
`sample_size`	No	Listings to sample, most relevant first (10-100).
`subcategory`	No	Subcategory name (e.g. 'Fietsen \| Racefietsen' or 'Fietsen \| Heren \| Herenfietsen') or numeric id. See list_categories with a parent.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`max`	No
`min`	No
`p25`	No
`p75`	No
`mean`	No
`note`	No
`site`	Yes
`query`	Yes
`median`	No
`cheapest`	No
`sample_size`	Yes
`total_count`	Yes
`excluded_outliers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Sep 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses concrete behavioral details: free, bidding-only and reserved ads are excluded, outliers beyond 1.5x IQR are trimmed, and statistics are based on the most relevant asking prices. This is genuine methodological transparency that an agent cannot infer from annotations.

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?

Three dense sentences: the first front-loads the core purpose, the second explains exclusions and outlier trimming, and the third gives a practical reliability tip. No filler or repetition of schema details.

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 14-parameter tool with 100% schema coverage, an output schema, and safety annotations, this description is complete enough. It explains the computation, exclusions, and reliability considerations; return values are covered by the output schema, so no further explanation is needed.

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 the baseline is 3. The description adds meaningful guidance beyond the schema by recommending subcategory plus attributes over free-text query and explaining that free text drags in accessories. This helps an agent choose better parameter combinations.

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?

The description names a specific verb and resource: it computes price statistics (min, quartiles, median, max, mean) and returns cheapest matches for a search. This is clearly distinct from sibling tools like search_listings or get_listing_details, so an agent can tell what the tool does 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?

The description gives clear context for how to use the tool: it operates over a search and is most reliable with a subcategory plus attributes rather than free text. It does not explicitly name alternatives or state when not to use it, but the context is strong enough to guide an agent.

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

Deploy Server