Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chrono24_listing

Fetch complete Chrono24 watch listing details including brand, model, price, condition, specs, photos, and seller info from a listing URL. Get structured JSON data for any watch listing.

Instructions

Get a Chrono24 watch listing's detail. Fetches one Chrono24 listing's full detail page: brand, model, reference number, price with currency and negotiability, condition, year of production, movement, case material and diameter, bracelet material, location, availability, seller type, photos, and the complete raw spec table Chrono24 itself shows (grouped by section: Basic Info, Caliber, Case, Bracelet/strap, Functions). path is the listing URL from a chrono24-search result's url field; Chrono24 has no lookup by numeric id alone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesListing URL or path from a chrono24-search result's url field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the comprehensive set of returned data (brand, model, price, condition, etc., plus the raw spec table) and the input requirement. It doesn't mention side effects, but as a read-only fetch operation, the behavior is clearly communicated.

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, front-loaded with the primary purpose, and the enumerated field list is informative without being redundant. Every sentence earns its place, and there is no filler.

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 simple one-parameter tool with no output schema, the description covers the input source, the full output contents, and a key constraint (no id lookup). Nothing an agent needs to call it correctly is missing.

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 schema already describes the 'path' parameter, but the description adds critical context: the path must be a listing URL from a chrono24-search result's url field, and numeric id alone will not work. This goes beyond the schema's brief description and prevents misuse.

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 opens with a specific verb and resource ('Get a Chrono24 watch listing's detail') and enumerates the exact fields returned. It also distinguishes itself from sibling tools like chrono24_search by noting the input path comes from a search result's url field, making it clear this is a single-listing detail fetcher.

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 explains the input prerequisite: the path must come from a chrono24-search result's url field, and explicitly warns that Chrono24 has no lookup by numeric id alone. This guides the agent on when to use this tool (after a search) and avoids a common pitfall, though it doesn't explicitly name alternative tools.

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

Deploy Server

Other Tools