Seasonal Buy-Sell Calendar
When a nameplate or body type sells cheapest and dearest in your state, month by month.
This is the technical reference. For the price, a rendered sample and answers to common questions, see the Seasonal Buy-Sell Calendar product page.
At a glance
| Price | $2.99 per run. |
| Tool name | generate_seasonal_buy_sell_calendar |
| Scope | reports:seasonal-buy-sell-calendar |
| Built for | Small Dealer, Dealer Group, Auctions & Wholesale |
What it does
Twelve months of sold-market data for one nameplate (make and model) or one body type in one US state, month by month: units that left dealer websites, the median asking price at exit, the median odometer and the median days to sell. Names the buy window (the three cheapest months with an adequate sample) and the sell window (the three dearest), the dollar swing between the cheapest and the dearest month, the busiest and quietest months, and the same twelve months nationally so a state pattern can be told from a national one. From the Sold Summary API: a sale is inferred when a listing leaves a dealer website, every price is the advertised asking price at exit (never a negotiated transaction price), and the data runs through the latest complete month. Use when a dealer, dealer group or wholesaler asks WHEN to buy or sell a nameplate or segment in their state, which months run cheapest or dearest, or how seasonal a market is. Do NOT use to rank what to stock without a nameplate in mind (use Market Movers), to plan trims and a max bid for one nameplate around a ZIP (use Stocking Guide), or to value one vehicle (use Vehicle Valuation Report). The sold data has state grain, not ZIP or radius. PRICING: $2.99 per run.
Arguments
| Argument | What it is | Example | |
|---|---|---|---|
state |
Required | US state, as a 2-letter code (e.g. TX). The sold data has state and city grain only, no ZIP or radius. | TX |
make |
Recommended | Make of the nameplate (e.g. Ford). Pass make and model for a nameplate calendar, or a body type for a segment. | Ford |
model |
Recommended | Model of the nameplate (e.g. F-150). Use with make. | F-150 |
body_type |
Recommended | A body type for a segment calendar instead of a nameplate: SUV, Sedan, Pickup, Hatchback, Minivan, Coupe, Wagon, Convertible, Cargo Van or Passenger Van. Add a make to narrow it (e.g. Toyota SUVs). | SUV |
inventory_type |
Optional | Which market: used (the default), new, or certified pre-owned. | used |
year_range |
Optional | Model years to include, e.g. 2020-2024. Leave blank for every model year. | 2020-2024 |
What comes back
- Buy window: the cheapest and the dearest month, the dollar swing between them, and the busiest and quietest months
- Twelve months of units sold, the priced sample, the median asking price, the median odometer and days to sell, with the buy and sell months marked
- The three buy months and three sell months, ranked only on months with an adequate sample
- State vs national: whether the swing and its timing match the national series
- The national 12-month sold trend for the same nameplate or segment
- Next steps: a Stocking Guide for the buy window and a monthly monitor for each new data month
Asking for it in a chat client
When is the best month to buy used pickups in Texas?
Show me the 12-month price and volume calendar for used RAV4s in Florida
Running it from a backend
Grant an agent the reports:seasonal-buy-sell-calendar scope, then call the tool over MCP:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "generate_seasonal_buy_sell_calendar",
"arguments": {
"state": "TX",
"make": "Ford",
"model": "F-150",
"inventory_type": "used"
}
}
}
See Server-side access for the token exchange and how to read the response.