Trim Contenting Report
Which trims of one model earn their place: volume, share, the asking-price band, sticker gap, turn and used-market retention.
This is the technical reference. For the price, a rendered sample and answers to common questions, see the Trim Contenting Report product page.
At a glance
| Price | $9.99 per run. |
| Tool name | generate_trim_contenting_report |
| Scope | reports:trim-contenting-report |
| Built for | Automaker |
What it does
The contenting read for one model, from Sold Summary API v2 at national grain: every trim with at least 10 units over the window (3 months by default), ranked by units, with its share of the model's units, the Low end, median and High end of advertised asking prices at exit, the gap to sticker (the average asking price against the average listing MSRP), the median days to sell and the priced sample, each from the trim's latest month with an adequate sample. Then the retention read: each trim's used median asking price for the most recent model years (3 by default) as a percent of its new median, with the used sample and odometer beside it. Three findings are written from the numbers: the volume core, which trims hold sticker and which are bought with discounts, and turn with used retention. Trims under the floor are counted and named, since trim names come from dealer listings and retired or misspelled names appear as thin rows. From the Sold Summary API: a sale is inferred when a listing leaves a US dealer website, every price is the advertised asking price at exit (never a negotiated transaction price), and options, packages and colours are not in the data. Use when a product planner, pricing analyst or contenting review asks which trims of a model sell, at what price and how far under sticker, which trims turn fastest, or how the trims hold value on the used side. Do NOT use for brand share against rivals (use Brand Share & Pricing Power), for a state discount map (use the Regional Discount & Scarcity Map), or for the model-year takeover (use the Model-Year Changeover Tracker). PRICING: $9.99 per run.
Arguments
| Argument | What it is | Example | |
|---|---|---|---|
make |
Required | Make of the model (e.g. Ford). | Ford |
model |
Required | The model (e.g. F-150), as the sold data spells it. | F-150 |
inventory_type |
Optional | Which market the trim table reads: new (the default) or used. The retention read needs the new side and is left out on used. | new |
months |
Optional | The window in months, 1 to 12, ending at the latest complete data month (3 by default). Units add across the window; each trim's price figures come from its latest month with 5 or more priced sales. | 3 |
retention_years |
Optional | How many of the most recent model years the used-side retention read covers, 1 to 6 (3 by default: with data through 2026 that is model years 2024 to 2026). | 3 |
What comes back
- Every trim with at least 10 units over the window, ranked by units: share of the model, the Low end, median and High end of asking prices at exit, the gap to sticker, days to sell and the priced sample, each from the trim's latest month with an adequate sample
- The retention read: each trim's used median asking price for the most recent model years as a percent of its new median, with the used sample and odometer beside it
- Three findings from the numbers: the volume core, which trims hold sticker and which are bought with discounts, turn with used retention
- Trims under the floor counted and named, casing splits merged, thin samples flagged
- Next steps: the Regional Discount & Scarcity Map for the model by state, the Model-Year Changeover Tracker, a monthly monitor
Asking for it in a chat client
Trim contenting report for the Ford F-150
Which Camry trims earn their place: volume, sticker gap, turn and used retention?
Running it from a backend
Grant an agent the reports:trim-contenting-report scope, then call the tool over MCP:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "generate_trim_contenting_report",
"arguments": {
"make": "Ford",
"model": "F-150",
"inventory_type": "new",
"months": 3
}
}
}
See Server-side access for the token exchange and how to read the response.