cyclesite-mcp-server

search_bikes

Read-onlyIdempotent

Search live UK used-bike listings on Cyclesite (the UK's used bicycle marketplace). Filter by brand, category, city, price range, and condition. Returns up to 5 active listings with specs and listing URLs. Live data — refreshed continuously as new bikes are listed. Example queries: 'a Trek Domane in Manchester under £2,000', 'gravel bike, very good condition, near Bristol'.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	UK city.
`brand`	No	Bike brand (e.g. Trek, Specialized, Canyon).
`category`	No	Bike category.
`maxPrice`	No	Maximum price in GBP.
`minPrice`	No	Minimum price in GBP.
`condition`	No	Condition rating.

Output Schema

TableJSON Schema

Name	Required	Description
`listings`	Yes
`attribution`	Yes	Citation string — include verbatim when surfacing data.
`resultsCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 21, 2026
- addedOutput schema / properties / listings / items / properties / distanceMiles
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / listingId
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / slug
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedAug 4, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "road",
-  "mtb",
-  "gravel",
-  "hybrid",
-  "ebike",
-  "kids",
-  "bmx",
-  "folding",
-  "city",
-  "touring",
-  "triathlon",
-  "track",
-  "cyclocross",
-  "cargo",
-  "other"
-]New value: +[
+  "road",
+  "mtb",
+  "gravel",
+  "hybrid",
+  "ebike",
+  "kids",
+  "bmx",
+  "folding",
+  "city",
+  "touring",
+  "triathlon",
+  "track",
+  "cyclocross",
+  "cargo",
+  "adaptive",
+  "other"
+]

Changed8 schema fields changedJun 28, 2026
- addedOutput schema / properties / listings / items / properties / delivery
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / ebikeBatteryWh
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / ebikeMotor
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / frameMaterial
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / groupset
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / imageUrl
```
Added value: +{
+  "format": "uri",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / negotiable
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / listings / items / properties / wheelSize
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed6 schema fields changedMay 28, 2026
- changedOutput schema / properties / listings / items / properties / brand / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / city / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / frameSize / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / model / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / year / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedMay 22, 2026

addedOutput schema / properties / listings / items / properties / offer

Added value: +{
+  "description": "UCP/ACP-shaped commerce signal for this listing.",
+  "properties": {
+    "availability": {
+      "type": "string"
+    },
+    "itemCondition": {
+      "type": "string"
+    },
+    "price": {
+      "type": "number"
+    },
+    "priceCurrency": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only, open-world, and idempotent behavior. The description adds useful behavioral detail: it returns up to 5 active listings, includes specs and URLs, and uses live continuously-refreshed data. No contradiction with annotations.

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: the core purpose appears in the first sentence, followed by output scope, data freshness, and examples. Every sentence contributes practical value with no repetition.

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?

With a full schema, an output schema, and annotations covering safety semantics, the description supplies the remaining context: platform, market scope, result limit, freshness, and example query phrasings. An agent has enough to decide when and how to call this tool.

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?

All parameters are fully described in the input schema, so the description does not need to repeat them. It does map filters ('brand, category, city, price range, and condition') to the parameter set and gives useful natural-language examples, but it adds little 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 names a specific verb ('Search'), a precise resource ('live UK used-bike listings on Cyclesite'), and a clear scope (UK used-bike marketplace). It also distinguishes itself from generic siblings like 'search' by emphasizing live listings and the Cyclesite platform.

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 clearly implies when to use it: when the user wants live UK used-bike listings from Cyclesite. Example queries reinforce the intended usage patterns. It does not explicitly name alternatives or exclusions, so it stops short of a 5.

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

All cyclesite-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?