Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bringatrailer_results

Search completed Bring a Trailer auctions and filter sold or reserve-not-met results by make, model, category, decade, keyword, model year, maximum bid, and recency.

Instructions

Bring a Trailer completed auctions. Pages through Bring a Trailer's archive of completed collector-vehicle auctions with final bids and sold or reserve-not-met results. Filter by make or model (ids from bringatrailer_makes), keyword, category, decade, origin, country, result, premium or no-reserve type, recency, model-year range, maximum bid and sort order. Every filter value is listed by bringatrailer_filters.

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

NameRequiredDescriptionDefault
qNoKeyword that must appear in the listing
eraNoComma-separated decade ids from bringatrailer_filters
makeNoMake name from bringatrailer_makes; mutually exclusive with model_id
pageNo1-based page
sortNoSort order
typeNoAuction type
originNoComma-separated origin ids from bringatrailer_filters
resultNoAuction result
countryNoComma-separated ISO 3166-1 alpha-2 country codes
excludeNoKeyword that must not appear in the listing
max_bidNoMaximum final bid in USD
recencyNoClosed within
categoryNoComma-separated category ids from bringatrailer_filters
max_yearNoMaximum model year
min_yearNoMinimum model year
model_idNoNumeric model id from bringatrailer_makes; mutually exclusive with make
per_pageNoResults per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior: the tool is read-only in effect (paging an archive), returns final bids and sold/reserve-not-met results, and supports pagination. It stops short of stating default page size, whether per_page is capped, how many results are reachable overall, or any rate-limit considerations, which matters for a 17-parameter archive crawler.

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?

Three sentences, front-loaded with the purpose and then the filter surface; no filler or marketing language. The long filter enumeration mildly duplicates the schema, but it functions as a scannable capability summary rather than wasted prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 17 optional parameters, no annotations, and no output schema, the description covers purpose and filter discovery but not result shape details such as what fields a listing carries beyond the final bid and sold status, total-count/end-of-results behavior, or defaults when no filters are supplied. Adequate, but a reader still has gaps before first invocation.

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 description coverage is 100%, so every parameter is already documented in the schema, including the make/model_id mutual exclusivity and the enum values. The description's filter enumeration largely restates the schema and the pointers to bringatrailer_makes and bringatrailer_filters duplicate what the schema descriptions already say, so it adds little meaning beyond structured data; baseline 3 applies.

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 opens with a specific verb+resource combination: paging through Bring a Trailer's archive of completed collector-vehicle auctions, returning final bids and sold / reserve-not-met outcomes. That clearly separates it from live-auction siblings in intent, though it never names a specific alternative (e.g. bringatrailer_live or bringatrailer_search), so an agent must infer the boundary from the phrase 'completed auctions'.

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 by 'completed auctions' plus the enumeration of supported filters, and it usefully points to bringatrailer_makes for make/model ids and bringatrailer_filters for enumerated filter values. However, there is no explicit statement of when to prefer this over bringatrailer_search, bringatrailer_live, or bringatrailer_listing, and no stated exclusions or prerequisites.

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

Deploy Server

Other Tools