cyclesite-mcp-server

find_similar_listings

Read-onlyIdempotent

Given a Cyclesite listing slug, return up to 5 similar active listings (same category, ±25% price, same brand or frame size weighted higher). Use when the user is interested in one bike and wants alternatives. Example: 'show me bikes like that one'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Source listing URL slug.

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.

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 declare readOnlyHint, openWorldHint, and idempotentHint. The description adds behavioral specifics beyond these: returns up to 5 results, filters by active status, and describes the similarity algorithm. This enhances understanding 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?

Two sentences: the first states core behavior with criteria, the second gives usage trigger and an example. No fluff, front-loaded with the most critical information.

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 one well-documented parameter and an output schema present, the description fully covers what the tool does, when to use it, and what it returns. It also includes an example of user intent, making it complete for an agent to select and invoke correctly.

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 schema has full coverage (100%) for the single 'slug' parameter with a clear description. The tool description repeats this ('Given a Cyclesite listing slug') but doesn't add syntax or format details, so it adds minimal value 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 clearly states the tool's function: 'return up to 5 similar active listings' given a listing slug. It specifies the exact similarity criteria (same category, ±25% price, brand/frame size weighting), which distinguishes it from sibling tools like search_bikes or get_recent_listings.

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?

Provides explicit when-to-use guidance: 'Use when the user is interested in one bike and wants alternatives' with a concrete example. While it doesn't mention exclusions or alternative tools, the stated use case is clear and contextually distinct.

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?