Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

bringatrailer_search

Search Bring a Trailer listings, model pages, past auctions with final prices, events, and stories by keyword; filter by section and page through the results.

Instructions

Search Bring a Trailer. Runs Bring a Trailer's site search and returns the matching live listings, make and model pages, previous auctions (sold, reserve not met and withdrawn, with final prices), past events and editorial stories, each with its own total. section narrows the response to one list and pages through it; every list pages 12 rows at a time except previous auctions at 24, and live listings (up to 100, repeated on every site page) come back only on page 1. A term that is exactly a make, model or category name (Ferrari, BMW 2002, boat) makes the site redirect to that page: the response then carries redirect and empty lists, and phrase=true runs the search instead. Member profiles are never returned.

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": {
      "q": "<q>"
    },
    "name": "bringatrailer_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesText to search, 2 to 100 characters without double quotes
pageNoPage number from 1
phraseNoMatch q as an exact phrase; needed when q is exactly a make, model or category name
sectionNoList to return: all (default), live_listings, models, previous_auctions, events or stories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/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 does so well: it discloses pagination granularity (12 rows per list, 24 for previous auctions), that live listings appear only on page 1 and are repeated site-wide, the redirect edge case and its payload shape, and an exclusion rule for member profiles. It omits any statement about access requirements, rate limits, or the per-row shape of returned items.

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?

Front-loaded with the core action and return types, then the operational caveats; every clause carries information. It is a single dense run-on paragraph with a mild redundancy between "Search Bring a Trailer" and "Runs Bring a Trailer's site search," which keeps it below the top mark.

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 four-parameter search tool with no output schema and no annotations, the definition covers return categories, counts, pagination quirks, and the redirect failure mode. Remaining gaps are what individual result rows contain and how the totals are surfaced, which the agent can only discover at call time.

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 beyond the schema: section both narrows and paginates, page interacts with different per-list page sizes, and phrase changes behavior from redirect to search. These are useful behavioral links but not format/syntax detail the schema lacks.

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?

States a specific verb and resource ("Search Bring a Trailer. Runs Bring a Trailer's site search") and enumerates the resource types returned: live listings, make/model pages, previous auctions, events, stories. It does not explicitly contrast with section-specific siblings such as bringatrailer_live or bringatrailer_results, so the agent must infer that this is the general entry point.

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?

Gives concrete operational guidance: use section to narrow to one list, use phrase=true when q is exactly a make/model/category name to avoid a redirect, and know that member profiles are never returned. What is missing is any explicit when-to-use-this-vs-alternative statement (e.g., versus the dedicated live/results tools).

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