Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chrono24_search

Search Chrono24 watch listings by keyword or browse a brand/model, filter by condition, material, movement, and more, returning prices, sellers, images, and listing URLs.

Instructions

Search Chrono24 watch listings. Searches Chrono24's luxury-watch marketplace by free-text keyword, or browses one brand's (optionally narrowed to one model's) current listings, returning result cards: title, price with currency, seller type, seller country, promotional badge, image, and the listing URL to pass to chrono24-listing. At least one of query or brand is required. Optional advanced-search filters (condition, used_or_new, case_material, dial_color, bracelet_material, movement_type, gender, watch_type, stock_info) narrow results further; each filter's accepted values are discoverable from chrono24-facets and echoed back in the response's filters field.

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based result page
sortNoResult order. One of: relevance, price_asc, price_desc, newest, popularity
brandNoBrand slug from chrono24-brands. At least one of query or brand is required
modelNoModel slug from chrono24-models (requires brand)
queryNoFree-text keyword search, e.g. \
genderNoAdvanced-search filter, values from chrono24-facets group=gender
conditionNoAdvanced-search filter, values from chrono24-facets group=condition
page_sizeNoResults per page. Chrono24's own UI offers 30, 60 or 120; defaults to Chrono24's own default
dial_colorNoAdvanced-search filter, values from chrono24-facets group=dialColor
stock_infoNoAdvanced-search filter, values from chrono24-facets group=stockInfo
watch_typeNoAdvanced-search filter, values from chrono24-facets group=watchType
used_or_newNoAdvanced-search filter, values from chrono24-facets group=usedOrNew
case_materialNoAdvanced-search filter, values from chrono24-facets group=caseMaterial
movement_typeNoAdvanced-search filter, values from chrono24-facets group=movementType
bracelet_materialNoAdvanced-search filter, values from chrono24-facets group=braceletMaterial

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.6/5.0
Behavior4/5

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

No annotations, so the description carries the burden and does well: it enumerates the returned card fields (title, price+currency, seller type/country, badge, image, URL), notes filters are echoed back in a filters field, and states the input constraint. It omits pagination/rate-limit/auth behavior, but the return contract is unusually well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose, followed by the constraint and then filter guidance. The long filter enumeration is dense but each clause earns its place; it is slightly long but not padded.

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 15-parameter, annotation-free tool with no output schema, the description covers purpose, both operating modes, the cross-parameter constraint, filter discovery, and the return shape. An agent has everything needed to invoke it correctly.

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?

Schema coverage is 100% (baseline 3), and the description adds real value on top: it documents the otherwise-invisible mutual requirement of query/brand (schema marks required as empty), explains brand/model slugs come from chrono24-brands/chrono24-models, and maps the filter params to chrono24-facets groups.

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?

States a specific verb+resource (search Chrono24 watch listings) and distinguishes two modes: free-text keyword search vs brand (optionally model) browsing. It also names the sibling it feeds into (chrono24-listing) and the facets/brands/models siblings for input lookup, so an agent can identify it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the selection condition ('At least one of query or brand is required'), routes filter-value discovery to chrono24-facets, and routes the returned listing URL to chrono24-listing. Alternatives and their triggering conditions are named. No explicit 'do not use' exclusion, but routing is complete enough to select correctly.

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