Crawlora MCP

bringatrailer_results

Read-only

Search Bring a Trailer's archive of completed collector-vehicle auctions (about 270,000) with final bids and sold or reserve-not-met results. make is a name from bringatrailer_makes and model_id is a models[].model_id from the same tool (use one, not both). category, era, origin and country take comma-separated values from bringatrailer_filters. result is sold or unsold, type is premium or noreserve, recency is 7D, 30D, 1Y, 2Y or 5Y, and sort is recent, oldest, popular or highest_bid. per_page is 10 to 50 (default 36). Returns auctions with title, URL, status, final price, end time, year, era, categories, country, flags, comment, watcher and view counts, excerpt and thumbnail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bringatrailer_results"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional. Keyword that must appear in the listing (for example 911 Turbo).
`era`	No	Optional. Comma-separated decade ids from bringatrailer_filters (for example 1970).
`make`	No	Optional. Make name exactly as listed by bringatrailer_makes (for example Porsche). Mutually exclusive with model_id.
`page`	No	Optional. 1-based page. Defaults to 1.
`sort`	No	Optional. recent (default), oldest, popular or highest_bid.
`type`	No	Optional. premium or noreserve.
`origin`	No	Optional. Comma-separated origin ids from bringatrailer_filters (for example 7 for German).
`result`	No	Optional. sold or unsold (reserve not met). Omit for both.
`country`	No	Optional. Comma-separated ISO 3166-1 alpha-2 country codes from bringatrailer_filters (for example US,CA).
`exclude`	No	Optional. Keyword that must not appear in the listing.
`max_bid`	No	Optional. Maximum final bid in USD.
`recency`	No	Optional. Closed within: 7D, 30D, 1Y, 2Y or 5Y. Omit for all time.
`category`	No	Optional. Comma-separated category ids from bringatrailer_filters (for example 434 for Convertibles).
`max_year`	No	Optional. Maximum model year (1885 to 2100).
`min_year`	No	Optional. Minimum model year (1885 to 2100).
`model_id`	No	Optional. Numeric model id from bringatrailer_makes (models[].model_id). Mutually exclusive with make.
`per_page`	No	Optional. Results per page, 10 to 50. Defaults to 36.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the archive's scope (~270,000), the meaning of result (sold vs reserve-not-met), recency windows, and the returned field set, which enriches understanding beyond the annotations.

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 dense sentences: the first front-loads purpose and scope, the second efficiently maps all filters. No filler, though the parameter sentence is a long run-on that could be split for readability.

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?

For a 17-parameter tool, the description covers filter sourcing, mutual exclusivity, defaults, and sort/recency options, and an output schema exists so return values are further defined. It is complete enough for confident invocation, with only explicit sibling routing as a minor gap.

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?

With 100% schema description coverage, the schema already documents each parameter, including valid sources (bringatrailer_filters, bringatrailer_makes). The description reinforces the mutual-exclusivity constraint and enumerates values, but largely repeats what the schema provides, so it earns the baseline rather than more.

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?

States a specific verb and resource (search the Bring a Trailer archive of completed collector-vehicle auctions) plus scope (about 270,000, with final bids and sold/reserve-not-met results). This clearly separates it from siblings like bringatrailer_live (active auctions) and bringatrailer_listing (single record).

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?

Explicitly notes make and model_id are mutually exclusive ('use one, not both') and directs the agent to bringatrailer_makes and bringatrailer_filters for valid filter values. It does not explicitly say when to prefer this over bringatrailer_live or bringatrailer_suggest, so usage context is strong but not complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP 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?