marktplaats-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Search for listings on Marktplaats.nl. Args: query: Search query text (required if no category specified) category: Main category name (e.g., "computers en software", "fietsen en brommers") subcategory: Subcategory name (e.g., "laptops", "elektrische fietsen") zip_code: Dutch postal code for distance calculations (e.g., "1016LV"). Required for distance filtering! distance_km: Maximum distance in kilometers (default: 1000). Only works with zip_code. price_from: Minimum price in euros price_to: Maximum price in euros condition: Item condition: "new", "as_good_as_new", "used", "refurbished", "not_working" seller_type: Filter by seller type: "business" (zakelijk, for VAT invoices) or "private" (particulier) sort_by: Sort method: "date", "price", "optimized", "location" sort_order: Sort order: "asc" or "desc" limit: Number of results (1-100, default: 10) offset: Pagination offset offered_since_days: Only show items posted within the last X days attribute_ids: List of attribute filter IDs (use get_category_filters to find these) extract_specs: Try to extract hardware specs (RAM, storage, CPU) from descriptions (for laptops/tablets) compact: Return minimal response format (~75% smaller). Omits description, image, links. Use get_listing_details(id) for full info. Seller: B=business, P=private. Condition: N=new, Z=as good as new, G=used, R=refurbished, D=defect. Returns: Dictionary with total_count, returned_count, and list of listings |
| get_listing_detailsB | Get full details of a specific listing including complete description and all images. Args: listing_id: The listing ID (e.g., "m2340580395") Returns: Full listing details including description, images, attributes, and seller info |
| get_seller_infoB | Get detailed information about a seller including ratings and verification status. Args: seller_id: The seller's numeric ID Returns: Seller profile with ratings, verification status, and statistics |
| list_categoriesB | List all available main categories and common subcategories on Marktplaats. Returns: Dictionary with main categories and subcategories |
| get_category_filtersA | Get available filter options for a specific category (like RAM, brand, screen size, etc.). Args: category: Main category name (e.g., "computers en software") subcategory: Subcategory name (e.g., "laptops") Returns: Available filters with their IDs that can be used in search_listings |
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 5 tools
Each tool targets a clearly distinct resource and action: search_listings for queries, get_listing_details for a single listing, get_seller_info for sellers, list_categories for the taxonomy, and get_category_filters for filter discovery. No two tools overlap in purpose.
All names follow a consistent snake_case verb_noun pattern (search_, get_, list_), with predictable pluralization of list-resources. No mixed conventions or vague verbs.
Five tools is well-scoped for a browsing-focused server; each earns its place and supports a distinct step in the search workflow (discover categories/filters, search, inspect listing, inspect seller).
The read-only search surface covers the full browsing lifecycle: category discovery, filter discovery, searching, listing details, and seller info. It lacks any write/favorite/messaging operations, though those may be intentionally out of scope for a search server.