chrono24-mcp

Overview Schema Source Related Servers Discussions Admin

Get watch details (batch)

get_watches

Read-only

Retrieve full Chrono24 listing details for up to 10 watch IDs in one request, including specs, photos, and dealer information.

Instructions

Get full details for a shortlist of up to 10 Chrono24 listing ids. Runs politely and sequentially; uncached ids take ~4s each.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	Yes	Up to 10 listing ids; each uncached id costs one polite request

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`count`	Yes
`watches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Sep 4, 2026

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "note": {
+      "type": "string"
+    },
+    "watches": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "availability": {
+            "description": "e.g. 'Item is in stock' - empty when the page does not say",
+            "type": "string"
+          },
+          "brand": {
+            "type": "string"
+          },
+          "canonicalUrl": {
+            "type": "string"
+          },
+          "caseDiameter": {
+            "type": "string"
+          },
+          "caseMaterial": {
+            "type": "string"
+          },
+          "condition": {
+            "type": "string"
+          },
+          "currency": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "error": {
+            "type": "string"
+          },
+          "gender": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "images": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "location": {
+            "type": "string"
+          },
+          "model": {
+            "type": "string"
+          },
+          "movement": {
+            "type": "string"
+          },
+          "priceDisplay": {
+            "type": "string"
+          },
+          "priceValue": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "reference": {
+            "type": "string"
+          },
+          "scope": {
+            "type": "string"
+          },
+          "sellerIds": {
+            "additionalProperties": false,
+            "description": "customerId powers get_dealer_listings; dealerId powers get_dealer_ratings",
+            "properties": {
+              "customerId": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "dealerId": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "customerId",
+              "dealerId"
+            ],
+            "type": "object"
+          },
+          "shipsWithin": {
+            "description": "Shipping estimate, e.g. '1 - 3 days'",
+            "type": "string"
+          },
+          "specs": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "year": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "brand",
+          "model",
+          "reference",
+          "priceDisplay",
+          "priceValue",
+          "currency",
+          "condition",
+          "year",
+          "movement",
+          "caseMaterial",
+          "caseDiameter",
+          "gender",
+          "scope",
+          "availability",
+          "description",
+          "location",
+          "images",
+          "specs"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "watches",
+    "note"
+  ],
+  "type": "object"
+}

First observedv0.4.0Aug 26, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds valuable behavioral context beyond the readOnlyHint/openWorldHint annotations by disclosing that it 'runs politely and sequentially' and that uncached ids take ~4s each. This gives the agent realistic performance and rate-behavior expectations without contradiction.

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 with no filler: the first front-loads the core purpose, and the second supplies relevant operational behavior. Every sentence 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?

For a single-parameter, read-only batched getter with an output schema and helpful annotations, the description supplies everything needed to invoke it correctly: resource, id format, batch limit, and pacing. No return-format explanation is required because the output schema exists.

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%, and the schema already documents ids as an array of numeric strings with minItems 1 and maxItems 10. The description's 'up to 10' and 'uncached ids take ~4s each' add runtime context but do not materially deepen parameter semantics 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 states a specific verb ('Get') and resource ('full details for a shortlist of up to 10 Chrono24 listing ids'), making the batch behavior explicit. The title's 'batch' and the 'up to 10' cap clearly distinguish it from the sibling get_watch without needing to name it.

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?

The description implies batch usage through 'shortlist' and 'up to 10,' and the latency note helps set expectations, but it never explicitly says when to prefer this over get_watch or search_listings. There is no direct when/when-not or alternative routing guidance, so an agent must infer usage from context.

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