chrono24-mcp

Overview Schema Source Related Servers Discussions Admin

Get dealer inventory

get_dealer_listings

Read-only

Retrieve a dealer's current watch inventory by providing their customerId, showing available listings in the same card format as search results.

Instructions

List a dealer's current inventory by their customerId (from get_watch's sellerIds). Same card shape as search_listings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`sort`	No		newest
`customerId`	Yes	Seller customerId from get_watch's sellerIds - powers a dealer's inventory

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`page`	Yes
`count`	Yes
`hasMore`	Yes
`currency`	Yes
`listings`	Yes
`sourceUrl`	Yes
`customerId`	Yes
`totalCount`	Yes
`totalPages`	Yes
`ignoredFacets`	No	Facet keys that were ignored because they are not passthrough params (e.g. countryIds -> use 'countries', usedOrNew -> use 'condition')

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.0Sep 4, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "customerId": {
+      "type": "string"
+    },
+    "hasMore": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ignoredFacets": {
+      "description": "Facet keys that were ignored because they are not passthrough params (e.g. countryIds -> use 'countries', usedOrNew -> use 'condition')",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "listings": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "badge": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "brandModel": {
+            "type": "string"
+          },
+          "detail": {
+            "type": "string"
+          },
+          "id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "imageUrl": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "location": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "negotiable": {
+            "type": "boolean"
+          },
+          "priceDisplay": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "priceValue": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "sellerType": {
+            "anyOf": [
+              {
+                "enum": [
+                  "dealer",
+                  "private"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "url",
+          "brandModel",
+          "detail",
+          "priceDisplay",
+          "priceValue",
+          "negotiable",
+          "location",
+          "sellerType",
+          "badge",
+          "imageUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "page": {
+      "type": "number"
+    },
+    "sourceUrl": {
+      "type": "string"
+    },
+    "totalCount": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "totalPages": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "customerId",
+    "totalCount",
+    "count",
+    "page",
+    "totalPages",
+    "hasMore",
+    "currency",
+    "listings",
+    "sourceUrl"
+  ],
+  "type": "object"
+}

First observedv0.4.0Aug 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral context by noting the inventory is 'current' and that the response has 'the same card shape as search_listings', giving the agent expectations about output consistency without needing to inspect the output schema.

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 compact and front-loaded with the core action and target resource. The second sentence provides a useful cross-tool reference without any fluff. Every sentence earns its place.

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?

For a simple read-only list endpoint with an output schema and safety annotations, the description covers the main purpose, the required parameter's source, and the expected card shape. It could be more explicit about pagination and sorting behavior, but the schema provides enough detail for those optional parameters, and the tool is otherwise complete enough to invoke correctly.

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?

The description reinforces the key parameter customerId and its provenance, which is helpful, but the schema already documents customerId. With schema description coverage at only 33%, page and sort are not explained in the description; however, their schema metadata (enum, default, min, max) partially compensates, so the description adds some but not enough meaning.

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 a specific verb ('List'), a specific resource ('a dealer's current inventory'), and the identifying key ('customerId'). It also ties the parameter to a specific source tool ('get_watch's sellerIds'), which distinguishes this tool from general search tools like search_listings.

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 gives clear context for when to use this tool: to fetch a dealer's current inventory using a customerId obtained from get_watch's sellerIds. It does not explicitly state when not to use it or name alternatives beyond the shape reference to search_listings, so it stops short of a full 5.

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