Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

bringatrailer_listing

Fetch a single Bring a Trailer auction's status, sold or high bid, end time, bid count, seller, location and lead image by slug or listing URL, optionally including full bid history.

Instructions

Get one Bring a Trailer auction. Returns one auction's detail: status, sold or high bid, end time, bid count, comments, views, watchers, seller, location, chassis, listing details, description and lead image. Pass the slug from /listing/{slug}/ or the full listing URL returned by the other endpoints. bid_history=true adds every bid (amount, currency, time, and any soft-close end-time extension) oldest first, without bidder names; it needs no extra request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "bringatrailer_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesListing slug or bringatrailer.com listing URL
bid_historyNoAdd the bid-by-bid history, without bidder names

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers: it lists the returned fields, discloses that bid_history yields bids oldest-first without bidder names and includes soft-close end-time extensions, and states it requires no extra request. It does not cover failure behavior for an invalid slug, but the behavioral picture is otherwise strong.

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?

The purpose comes first, followed by the returned fields and then the two parameter behaviors, so it is front-loaded and easy to scan. The long field enumeration is dense but every item tells the agent what it can rely on, so it earns its space.

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?

There is no output schema and no annotations, so the description must supply the return shape and behavior itself, which it does by enumerating the detail fields and explaining the bid_history expansion. For a two-parameter read tool this is close to complete, with only error and edge-case handling left unstated.

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 coverage is 100%, so the baseline is 3, and the description does add real meaning: slug accepts either a bare slug or a full bringatrailer.com URL, and bid_history is explained as an additive, no-extra-request expansion that omits bidder names. This is moderate added value over an already complete schema rather than a large lift.

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 leads with a specific verb and resource ("Get one Bring a Trailer auction") and enumerates the detail fields returned, making the single-listing scope unambiguous. It never names a sibling such as bringatrailer_search or bringatrailer_results, so the differentiation is implied by "one auction" rather than stated.

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 only implied: the mention that the slug comes from /listing/{slug}/ or from "the other endpoints" suggests this is the drill-down after a search or results call, but no explicit when-to-use or when-not-to-use is stated. The bid_history note gives practical guidance for that parameter but not for choosing this tool over alternatives.

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