cyclesite-mcp-server

Search bikes for sale

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'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_bikes"
  }
}

Input 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

Name	Required	Description
`listings`	Yes
`attribution`	Yes	Citation string for the data in this result.
`resultsCount`	Yes
`searchedFrom`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedOutput schema / properties / attribution / description

Previous value: -"Citation string — include verbatim when surfacing data."New value: +"Citation string for the data in this result."

Changed1 schema field changedOct 28, 2026
- addedOutput schema / properties / searchedFrom
```
Added value: +{
+  "type": "string"
+}
```
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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile carries no burden on the description. The description usefully adds that results are capped at 5 active listings, include specs and URLs, and come from continuously refreshed live data. It stops short of disclosing pagination behaviour, sort order, or what happens with zero matches, which matters for a live-index search returning a small fixed page. The 'openWorldHint: false' annotation sits in mild tension with a live external marketplace, though not enough to call a contradiction.

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?

The description is front-loaded with the core purpose, then filters, then return shape and freshness, with example queries at the end. Four short sentences with no filler; the examples earn their place by showing multi-filter composition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values in depth, and it covers result count, contents, and data freshness adequately for an all-optional 6-parameter search. The remaining gap is operational: no mention of pagination, sorting, or empty-result behaviour, which an agent would want for this kind of capped live search.

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 both enums are self-explanatory, so the schema already does the heavy lifting and baseline 3 applies. The description adds marginal value by mapping natural-language phrasing ('under £2,000', 'near Bristol') onto the price and city parameters, but gives no guidance on default behaviour when filters are omitted or on how city matching works.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Search live UK used-bike listings on Cyclesite') and enumerates the filterable dimensions, so the agent knows exactly what the tool retrieves. It does not differentiate from sibling tools such as 'search', 'search_by_location', or 'find_similar_listings', which overlap in purpose, leaving the agent to infer which one to pick.

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?

Usage is only implied, through example queries like 'a Trek Domane in Manchester under £2,000' that show how to compose filters. There is no explicit statement of when this tool is preferred over 'search' or 'search_by_location', nor any prerequisite or exclusion guidance.

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?