chrono24-mcp

Overview Schema Source Related Servers Discussions Admin

Search Chrono24 listings

search_listings

Read-only

Search Chrono24 watch listings by query, brand, model, or reference number, and filter by price, condition, location, and more. Get up to 60 concise results per page for quick shortlisting.

Instructions

Search Chrono24 watch listings. Returns up to 60 cards per page with id, url, title, price, location, seller type and thumbnail - enough to shortlist without fetching details. Free-text queries match fuzzily; for a precise model scope pass manufacturerIds + models (from find_models) or referenceNumber.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	1-based page number (60 results per page)
`sort`	No	Sort order	newest
`year`	No	Year of production filter
`limit`	No	Cap the number of listings returned (1-60); useful for shortlisting without parsing a full page
`query`	No	Free-text search, e.g. 'Rolex Submariner'. Optional when filtering by manufacturerIds/models/reference instead
`facets`	No	Extra facet filters as param->value pairs, e.g. {"caseMaterials": "4", "braceletMaterial": "407"}. Common names: caseMaterials, braceletMaterial, dialColors, gender, movementTypes, watchCategories, maxAgeInDays - values via list_filters
`models`	No	Chrono24 numeric model id (digits from --mod URLs)
`priceTo`	No	Maximum price
`certified`	No	Only Chrono24 Certified listings
`condition`	No	Condition filter
`countries`	No	ISO2 country codes to filter seller location, e.g. ['US','DE','CH']
`priceFrom`	No	Minimum price
`manufacturerIds`	No	Chrono24 numeric brand id (Rolex=221). Optional; query text usually suffices
`referenceNumber`	No	Reference number filter, e.g. '116610lv'

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`page`	Yes
`count`	Yes
`hasMore`	Yes
`currency`	Yes
`listings`	Yes
`sourceUrl`	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.

Changed13 schema fields changedv0.6.0Sep 4, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / facets / description

Previous value: -"Extra facet filters as param->value pairs, e.g. {\"caseMaterials\": \"4\", \"braceletMaterial\": \"407\"}. Discover names/values via list_filters"New value: +"Extra facet filters as param->value pairs, e.g. {\"caseMaterials\": \"4\", \"braceletMaterial\": \"407\"}. Common names: caseMaterials, braceletMaterial, dialColors, gender, movementTypes, watchCategories, maxAgeInDays - values via list_filters"

addedInput schema / properties / facets / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

changedInput schema / properties / priceFrom / description

Previous value: -"Minimum price in USD"New value: +"Minimum price"

addedInput schema / properties / priceFrom / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / priceFrom / minimum
```
Added value: +-9007199254740991
```

changedInput schema / properties / priceTo / description

Previous value: -"Maximum price in USD"New value: +"Maximum price"

addedInput schema / properties / priceTo / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / priceTo / minimum
```
Added value: +-9007199254740991
```
addedInput schema / properties / year / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / year / minimum
```
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"
+    },
+    "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": [
+    "totalCount",
+    "count",
+    "page",
+    "totalPages",
+    "hasMore",
+    "currency",
+    "listings",
+    "sourceUrl"
+  ],
+  "type": "object"
+}

First observedv0.4.0Aug 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavioral context: it returns up to 60 cards per page, lists the exact fields included, and notes fuzzy free-text matching. This goes beyond the structured annotations without contradicting them.

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?

Three sentences, each earning its place: the first states the purpose, the second summarizes return shape and shortlisting use, and the third gives parameter strategy. No filler or redundancy.

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?

For a read-only search tool with an output schema and fully documented parameters, the description is complete: it covers result page size, returned fields, fuzzy vs. precise search, and the relationship to find_models. Nothing critical is missing for an agent to decide whether and how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% parameter description coverage, so the baseline is 3, but the description adds useful cross-parameter guidance: query is optional when filtering by manufacturerIds/models/reference, and precise model search depends on find_models. This helps the agent choose the right parameter combination rather than just understanding individual fields.

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 names a specific action ('Search') and a specific resource ('Chrono24 watch listings'), and immediately distinguishes the tool's value by describing the card fields returned. It is clearly differentiated from siblings like search_all or get_dealer_listings by focusing on listing search and shortlisting without detail fetching.

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 provides clear context on how to search: free-text queries are fuzzy, and precise model scoping should use manufacturerIds + models from find_models or referenceNumber. It stops short of explicitly stating when to prefer sibling tools like search_all or get_dealer_listings, but the guidance is clear and actionable.

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