marktplaats-mcp

Overview Schema Source Related Servers Discussions Admin

Get seller profile

get_seller_profile

Read-onlyIdempotent

Retrieve a seller's trust signals: verified identity, bank, phone, business status, payment method, review score and count to assess reliability on Marktplaats or 2dehands.

Instructions

Look up a seller's trust signals: verified bank account / identity / phone number, business verification, payment method, review score and count. Null means the marketplace does not report that signal. Use list_seller_listings to see everything the seller currently offers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`site`	No	Which marketplace: marktplaats (Netherlands) or 2dehands (Belgium).	marktplaats
`seller_id`	Yes	Numeric seller id from a listing's seller field.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`site`	Yes
`seller_id`	Yes
`average_score`	No
`payment_method`	No
`business_verified`	No
`number_of_reviews`	No
`bank_account_verified`	No
`phone_number_verified`	No
`identification_verified`	No
`low_bid_threshold_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.0Sep 26, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "average_score": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Average Score"
+  },
+  "bank_account_verified": {
+    "anyOf": [
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Bank Account Verified"
+  },
+  "business_verified": {
+    "anyOf": [
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Business Verified"
+  },
+  "identification_verified": {
+    "anyOf": [
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Identification Verified"
+  },
+  "low_bid_threshold_percent": {
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Low Bid Threshold Percent"
+  },
+  "number_of_reviews": {
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Number Of Reviews"
+  },
+  "payment_method": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Payment Method"
+  },
+  "phone_number_verified": {
+    "anyOf": [
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Phone Number Verified"
+  },
+  "seller_id": {
+    "title": "Seller Id",
+    "type": "integer"
+  },
+  "site": {
+    "title": "Site",
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "seller_id",
+  "site"
+]

addedOutput schema / title
```
Added value: +"SellerProfile"
```

First observedv0.1.1Jul 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the important interpretation that null means the marketplace does not report that signal, which helps the agent avoid misreading missing data as a problem.

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?

Two sentences deliver the core purpose, the null semantics, and a cross-reference to a sibling tool with no filler. Everything earns its place.

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?

Annotations cover safety and idempotency, an output schema exists, parameters are fully documented, and the description provides the one interpretive detail an agent needs: what null means. Nothing essential is missing.

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 description coverage is 100%, so parameters are already fully documented in the schema. The description does not add much beyond indicating the seller context; per the rubric, baseline 3 is appropriate when the schema carries the parameter-semantics load.

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?

Description opens with a specific verb-resource pair ('Look up a seller's trust signals') and enumerates concrete signal types. It also names list_seller_listings as the sibling for current offerings, which distinguishes this tool from a nearby alternative.

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 the tool is for trust/verification data rather than active listings, and explicitly points to list_seller_listings when the agent needs current offers. It provides a clear context signal, though it does not spell out exhaustive when-not-to-use conditions.

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

Deploy Server