cyclesite-mcp-server

get_recent_listings

Read-onlyIdempotent

What's new on Cyclesite right now — up to 10 of the freshest active UK listings, refreshed every 15 minutes. Use when the user asks 'what's new today?' or 'any new road bikes this week?' rather than for a specific filter. Optional category + maxPrice filters. Live data.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	How many listings to return (1-10, default 10).
`category`	No
`maxPrice`	No	Maximum price in GBP.

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. Dates show when Glama detected each change.

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.7/5.0

Behavior5/5

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

Beyond the readOnly and idempotent hints, the description reveals specific behavioral traits: a 15-minute refresh cycle, a maximum of 10 results, and filtering options. It also discloses the data scope ('active UK listings') and liveness, giving agents a clear mental model of what to expect without contradicting 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 concise and front-loaded with the core purpose, followed by usage context, filter notes, and a liveness statement. Every sentence contributes meaningful information, with no wasted words or redundant elaboration.

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?

Given the simple tool (3 optional params, output schema exists), the description covers all key aspects: purpose, when to use, filters, freshness, and scope. There is no need to explain return values since an output schema is present, and the description is complete for an agent to decide correct invocation.

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?

The description adds minimal semantic value for parameters: it notes 'Optional category + maxPrice filters,' which clarifies their role but does not detail category values or interactions. Schema coverage is 67%, with category lacking a description; the enum provides the list, and limit and maxPrice have schema descriptions. The description does not fully compensate for category's missing description but is adequate.

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 clearly states the tool returns the freshest active UK listings, with a concrete scope (up to 10, refreshed every 15 minutes). It also distinguishes itself from siblings by explicitly stating it is not for specific filters, making the purpose and boundaries unambiguous.

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?

It provides explicit when-to-use guidance with example queries ('what's new today?', 'any new road bikes this week?') and directly contrasts with 'specific filter' use cases, implying alternatives like search. This is strong contextual guidance beyond a generic 'use for recent listings.'

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?