marktplaats-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARKTPLAATS_MAX_RETRIES | No | Retries after the first attempt. Clamped to 0-10. | 3 |
| MARKTPLAATS_MIN_INTERVAL_MS | No | Minimum gap between request starts in milliseconds. Clamped to 0-60000. | 1000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Search marktplaats.nl (Dutch classifieds) for products. Returns price, condition, delivery, category specs, location and seller for each hit. delivery is "shipping", "pickup", "both" (seller offers either) or "unknown". Paid placements are included and flagged with isSponsored. Prices are euros; priceEur is null when a listing takes bids or names no price. |
| get_listingA | Fetch full detail for one listing by id or URL. Adds what search does not carry: shipping carrier and transit days, view and favourite counts, listed-since date, seller tenure, category path, bidding and reserved state, and the full description. |
| get_sellerA | Fetch a seller's public profile by numeric seller id, as returned in search results. Useful for judging whether a seller is a private person or a shop. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct resource: search_listings searches the marketplace, get_listing fetches one listing's details, and get_seller fetches a seller's profile. There is no overlap between these operations.
All tool names follow a consistent verb_noun pattern: search_listings, get_listing, get_seller. Naming style is uniform snake_case with clear verbs.
Three tools is an appropriate, well-scoped set for a read-only classifieds search server. Each tool is essential and there is no redundancy.
The core read workflows (search, view detail, view seller) are covered, which is sufficient for a marketplace lookup server. However, the surface lacks a direct way to list all listings by a seller (or other browse/filter operations), which would round out the domain.