Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

autotrader_search

Search Autotrader new and used vehicle listings by make, model, price, mileage, year, location, condition, or body style; returns vehicle summaries and total match count.

Instructions

Search Autotrader vehicle listings. Searches Autotrader for new and used car listings, returning vehicle summaries (make, model, trim, year, mileage, pricing, images) plus the total matching count.

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit US ZIP code to search around
makeNoAutotrader make code, e.g. TOYOTA, HONDA, BMW
pageNo1-indexed result page, defaults to 1. Autotrader returns 24 results per page
trimNoAutotrader trim code. Requires make and model
modelNoAutotrader model code, e.g. CAMRY. Requires make
queryNoFree-text keyword search
radiusNoSearch radius in miles around zip
max_yearNoMaximum model year
min_yearNoMinimum model year
conditionNoListing condition. Allowed values: new, used, certified, 3p_cert
max_priceNoMaximum price in US dollars
min_priceNoMinimum price in US dollars
body_styleNoBody style. Allowed values: convertible, coupe, hatchback, sedan, suv, truck, van, wagon
max_mileageNoMaximum odometer mileage
seller_typeNoSeller type. Allowed values: dealer, private

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / body_style / enum
      Added value: +[
+  "convertible",
+  "coupe",
+  "hatchback",
+  "sedan",
+  "suv",
+  "truck",
+  "van",
+  "wagon"
+]
    • addedInput schema / properties / condition / enum
      Added value: +[
+  "new",
+  "used",
+  "certified",
+  "3p_cert"
+]
    • addedInput schema / properties / seller_type / enum
      Added value: +[
+  "dealer",
+  "private"
+]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does usefully disclose the return shape (vehicle summaries plus total matching count), which is beyond the schema, but it says nothing about pagination behavior, rate limits, or auth needs that a caller should know.

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

Conciseness5/5

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

Two sentences, front-loaded with the core purpose and then the return contents. Every clause earns its place with no redundancy.

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?

No output schema exists, but the description compensates by listing the returned fields and the total count. Combined with a fully documented 15-parameter schema, an agent has enough to invoke it correctly, with only minor gaps around pagination framing.

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%, with all 15 parameters documented (including enum values and cross-field requirements like trim requiring make and model), so the schema does the heavy lifting. The description adds no parameter meaning beyond that, matching the baseline 3.

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 gives a specific verb and resource ("Search Autotrader vehicle listings") and even enumerates the returned fields (make, model, trim, year, mileage, pricing, images) plus the total count. It is clearly a search tool, but it offers no differentiation from adjacent search siblings such as carsdotcom_search or carmax_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no exclusions or named alternatives. Usage is only implied by the word "Search" and the mention of "new and used car listings"; an agent gets no help deciding this over autotrader_vehicle or a competitor search tool.

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