Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

bringatrailer_live

List live Bring a Trailer auctions with bids and end times, then filter by title, category, decade, country, ending window, max bid, premium, or no-reserve status and sort by ending soon or bid.

Instructions

List live Bring a Trailer auctions. Returns the auctions currently open on Bring a Trailer (about 1,300) with current bid, end time and attributes. Filter by title text, category, decade, country, ending window, maximum current bid and the premium and no-reserve flags; sort by ending soon, highest bid or lowest bid.

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_live"
  }
}

Input Schema

Name	Required	Description
`q`	No	Case-insensitive text that must appear in the title
`era`	No	Comma-separated decade ids from bringatrailer_filters
`page`	No	1-based page
`sort`	No	Sort order
`country`	No	Comma-separated ISO 3166-1 alpha-2 country codes
`max_bid`	No	Only auctions whose current bid is at most this many USD
`premium`	No	Only premium auctions
`category`	No	Comma-separated category ids from bringatrailer_filters
`per_page`	No	Results per page
`no_reserve`	No	Only no-reserve auctions
`ending_within`	No	Only auctions ending within this many hours

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.5/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 behavioral burden. It does disclose useful context: the result magnitude (~1,300 live auctions) and the shape of returned data (current bid, end time, attributes), and 'List' implies a read-only operation. However it says nothing about pagination limits, ordering defaults, or freshness/refresh cadence for a real-time auction feed.

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, front-loaded with purpose and scope before the filter enumeration, with no filler. The second sentence duplicates the schema's parameter list fairly closely, which is slightly redundant but still aids fast scanning.

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 an 11-parameter, no-annotation, no-output-schema tool, the description covers what the tool returns and what can be filtered, which is the main gap an output schema would otherwise fill. Remaining gaps are pagination behavior and defaults, which the schema partially handles via page/per_page.

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 all 11 parameters are already documented with their own semantics, which sets the baseline at 3. The description's filter/sort enumeration largely restates the schema and adds no format details (e.g., that era and category ids come from bringatrailer_filters, which the schema covers).

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 names a specific verb and resource ('List live Bring a Trailer auctions') and states scope ('auctions currently open ... about 1,300') plus returned fields (current bid, end time, attributes). It implicitly separates itself from results/ended-auction tools via 'live', but never names a sibling explicitly, so it falls just short of a 5.

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 is implied by the word 'live' and by the enumerated filter and sort options, so an agent can infer this is the browse-what's-open-now tool. There is no explicit when-to-use/when-not guidance and no named alternative such as bringatrailer_results for completed auctions.

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

Deploy Server