cyclesite-mcp-server

Mark sold

mark_as_sold

DestructiveIdempotent

Mark a Cyclesite listing as sold, optionally with the final sale price, where it sold and the date it sold. Requires OAuth scope listings:manage. Example: 'mark my Trek Domane as sold for £1,750 on Facebook last Saturday'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listingId": "<listingId>"
    },
    "name": "mark_as_sold"
  }
}

Input Schema

Name	Required	Description
`soldOn`	No	The day it sold, YYYY-MM-DD. Leave out for today. Ignored if in the future or before the listing went up.
`listingId`	Yes
`saleVenue`	No	Where the sale was agreed.
`salePriceGbp`	No	What it actually sold for. Leave out if the seller did not say.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / saleVenue / enum

Previous value: -[
-  "cyclesite",
-  "facebook",
-  "ebay",
-  "gumtree",
-  "elsewhere"
-]New value: +[
+  "cyclesite",
+  "facebook",
+  "ebay",
+  "gumtree",
+  "other_bike_site",
+  "elsewhere"
+]

Changed3 schema fields changedSep 16, 2026

addedInput schema / properties / salePriceGbp / description

Added value: +"What it actually sold for. Leave out if the seller did not say."

addedInput schema / properties / saleVenue

Added value: +{
+  "description": "Where the sale was agreed.",
+  "enum": [
+    "cyclesite",
+    "facebook",
+    "ebay",
+    "gumtree",
+    "elsewhere"
+  ],
+  "type": "string"
+}

addedInput schema / properties / soldOn

Added value: +{
+  "description": "The day it sold, YYYY-MM-DD. Leave out for today. Ignored if in the future or before the listing went up.",
+  "type": "string"
+}

First observedMay 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds a genuinely non-structured fact, the required OAuth scope `listings:manage`, which an agent needs before attempting the call. It stops short of saying whether the change is reversible or what happens to open enquiries.

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?

Two sentences and a short example, front-loaded with the core action before the optional detail. The example earns its place by demonstrating how free-form user phrasing maps onto the price, venue and date parameters.

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?

An output schema and rich annotations exist, so return values and safety hints need not be restated. The description covers auth scope, optional fields and input shape; only post-sale side effects (impact on reservations, enquiries, listing visibility) are left unaddressed.

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 coverage is 75%, with only listingId undocumented. The description names the three optional values (price, venue, date) but adds little syntax beyond the schema; the one useful extra is the 'last Saturday' phrasing, which signals that relative dates are acceptable input and must be resolved to YYYY-MM-DD.

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 gives a specific verb and resource ('Mark a Cyclesite listing as sold') plus the optional attributes that can be captured. It is clearly distinct from siblings such as reserve_listing or publish_listing by implication, though it never names them.

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 context is implied through the natural-language example and the required OAuth scope, which tells the agent the caller must hold `listings:manage`. There is no explicit guidance on when to prefer this over reserve_listing or how to handle a listing that is already reserved or sold.

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?