Skip to main content
Glama
jasp-nerd

marktplaats-mcp

Search listings

search_listings
Read-onlyIdempotent

Search second-hand listings on Marktplaats or 2dehands with filters for category, price, condition, recency, and distance from a postal code.

Instructions

Search second-hand listings on Marktplaats or 2dehands with filters for category, price range, condition, recency and distance from a postal code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoWhich marketplace: marktplaats (Netherlands) or 2dehands (Belgium).marktplaats
limitNoResults per page (1-100).
queryNoFree-text search, e.g. 'racefiets' or 'iphone 15'. May be empty if a category is given.
offsetNoPagination offset: page_number * limit.
compactNoTrue (default) returns a token-efficient shortlist; False adds description, seller, images and attributes per listing.
sort_byNo'relevance' (default), 'date' (newest first with desc), 'price' or 'location'.relevance
categoryNoTop-level category name (Dutch, e.g. 'Fietsen en Brommers') or numeric id. See list_categories.
postcodeNoDutch/Belgian postal code to search around, e.g. '1011 AB' or '2000'. Required for distance filtering.
price_toNoMaximum price in euros.
conditionNoFilter by item condition.
price_fromNoMinimum price in euros.
sort_orderNo'asc' or 'desc'.desc
distance_kmNoMax distance from postcode in kilometers.
subcategoryNoSubcategory name (e.g. 'Fietsen | Racefietsen') or numeric id.
include_sponsoredNoInclude paid promotions (DAGTOPPER/TOPADVERTENTIE) and the sponsored top block.
offered_since_daysNoOnly listings placed within the last N days.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description does not add behavioral context beyond the purpose, but it is consistent with 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?

Single sentence efficiently conveys core functionality without redundancy. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 parameters fully documented in schema, an output schema, and sibling tools listed, the description adequately covers the tool's scope. Slightly brief for the complexity but sufficient.

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% with thorough descriptions. The description summarizes filter types but adds no new meaning beyond the 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?

The description clearly states the tool searches second-hand listings on named platforms with specific filter types, distinguishing it from siblings like check_new_listings or list_categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description lists filters, it does not explicitly instruct when to use this tool versus alternatives or provide exclusion criteria. Usage is implied but not guided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jasp-nerd/marktplaats-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server