Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_vehicle_listings_search

Search used-vehicle listings from CarMax, Autotrader, and Cars.com by make, model, price, mileage, and location. Filter and sort results to find specific cars.

Instructions

Search vehicle listings dataset. Searches the crawled used-vehicle listings index. source enum: carmax, autotrader, carsdotcom. CarMax's own national inventory is fully enumerable (re-crawled on a standing schedule); Autotrader/Cars.com coverage is a best-effort zip-code sweep, not exhaustive, and their rows approximate city/state from the searched area rather than the seller's exact location. seller_type enum: retailer, dealer, private (not populated for every row -- see the dataset markdown). Sort enum: relevance, recently_updated, newly_listed, price_asc, price_desc, mileage_asc, mileage_desc, year_desc, year_asc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over make, model and trim, max 256 characters
vinNoExact VIN filter. Best-effort: not guaranteed on every listing
makeNoExact make filter (e.g. Honda, Toyota), max 128 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, recently_updated, newly_listed, price_asc, price_desc, mileage_asc, mileage_desc, year_desc, year_asc
trimNoExact trim filter, max 128 characters
modelNoExact model filter (e.g. Civic), max 128 characters
stateNoExact US state abbreviation filter (e.g. CA), max 8 characters
run_idNoExact crawl run-id filter, max 128 characters
sourceNoExact source marketplace filter: carmax, autotrader, carsdotcom
max_yearNoMaximum model year
min_yearNoMinimum model year
fuel_typeNoExact fuel type filter (e.g. Gas, Hybrid, Electric), max 128 characters
max_priceNoMaximum price in US dollars
min_priceNoMinimum price in US dollars
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
body_styleNoExact body style filter (e.g. Sedan, SUV), max 128 characters
drive_typeNoExact drivetrain filter, max 128 characters
max_mileageNoMaximum odometer mileage
seller_typeNoExact seller type filter: retailer, dealer, private
transmissionNoExact transmission filter, max 128 characters
is_price_reducedNoFilter for listings currently marked down from a previous price

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / seller_type / enum
      Added value: +[
+  "retailer",
+  "dealer",
+  "private"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "recently_updated",
+  "newly_listed",
+  "price_asc",
+  "price_desc",
+  "mileage_asc",
+  "mileage_desc",
+  "year_desc",
+  "year_asc"
+]
    • addedInput schema / properties / source / enum
      Added value: +[
+  "carmax",
+  "autotrader",
+  "carsdotcom"
+]
  2. Addedv1.16.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries full burden and it does disclose significant behavioral traits: coverage is not uniform by source, Autotrader/Cars.com rows approximate city/state rather than seller location, and seller_type can be missing. This goes beyond the schema and gives agents a realistic model of data caveats, though it omits details like pagination cap or result shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description packs useful caveats into a single dense paragraph, but it also repeats the source, seller_type, and sort enums that are already fully specified in the schema. Redundant enum listing prevents top marks, while the unique coverage caveats are front-loaded and valuable.

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?

For a 22-parameter search tool with no annotations and no output schema, the description covers data caveats well but leaves some gaps: it doesn't describe the result structure, mention the page * page_size <= 10000 constraint (schema does), or tell the agent that item-level detail is available via datasets_vehicle_listings_item. The coverage derisking is strong, but the missing guidance on downstream retrieval and return shape keeps it at a mid score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all 22 parameters at 100% coverage, so baseline is 3. The description adds meaningful semantics for the source and seller_type enums by explaining coverage quality and the 'not populated for every row' caveat, and it lists sort values for convenience. That extra context lifts it above baseline.

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 vehicle listings dataset' and 'Searches the crawled used-vehicle listings index.' It clearly positions itself as the dataset search rather than a live marketplace scrape, though it never names sibling tools like datasets_vehicle_listings_item or the live source searches, so differentiation is clear but not explicit.

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?

The description gives important context on when the dataset is reliable ('CarMax's own national inventory is fully enumerable... Autotrader/Cars.com coverage is a best-effort zip-code sweep'), but it never tells the agent when to choose this over alternatives (e.g., live carmax_search/autotrader_search/carsdotcom_search, or the item/facets siblings). Usage is implied rather than stated.

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