Skip to main content
Glama
jasp-nerd

marktplaats-mcp

Get seller profile

get_seller_profile
Read-onlyIdempotent

Retrieve a seller's verified bank account, identity, phone number, review score, and review count to assess trustworthiness on Marktplaats and 2dehands.

Instructions

Look up a seller's trust signals: verified bank account / identity / phone number, review score and number of reviews.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoWhich marketplace: marktplaats (Netherlands) or 2dehands (Belgium).marktplaats
seller_idYesNumeric seller id from a listing's seller field.

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 false, so the description is not required to disclose these. The description adds context on returned data (trust signals) but no new behavioral traits beyond what annotations provide.

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?

The description is a single, concise sentence that conveys the tool's purpose without unnecessary words. Front-loaded and efficient.

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?

Given the tool's simplicity, annotations, and presence of an output schema, the description is complete. No missing behavioral or parameter details are needed.

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 both parameters described. The description does not add extra meaning beyond the schema. Baseline 3 is appropriate.

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 it looks up a seller's trust signals, listing specific items (verified bank account, identity, phone number, review score, number of reviews). It distinguishes from siblings like get_listing_details and search_listings, which deal with listings rather than seller profiles.

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 implies use when needing seller trust information. Sibling tools focus on listings, so context is clear. However, it lacks explicit 'when not to use' or alternative recommendations.

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