Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

carsdotcom_search

Search Cars.com new and used vehicle listings by ZIP, radius, page, or condition to return car summaries and total matching count.

Instructions

Search Cars.com vehicle listings. Searches Cars.com for new and used car listings, returning vehicle summaries (make, model, trim, year, mileage, exterior color, drivetrain, fuel type, pricing, seller, images) plus the total matching count.

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit US ZIP code to search around
pageNo1-indexed result page, defaults to 1. Cars.com returns 24 results per page
radiusNoSearch radius in miles around zip
stock_typeNoListing condition. Allowed values: new, used, cpo, all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / stock_type / enum
      Added value: +[
+  "new",
+  "used",
+  "cpo",
+  "all"
+]
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the returned fields and the total matching count, which is useful behavioral context, but omits auth requirements, rate limits, and that 24 results per page come back (only documented in the schema's page parameter).

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 that are tightly scoped and front-load purpose. Minor redundancy between 'Search Cars.com vehicle listings' and 'Searches Cars.com for new and used car listings', but overall efficient.

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 search tool with a fully documented schema and no output schema, the description covers purpose and return contents adequately. The main gap is usage guidance and pagination behavior, but nothing critical to invoking the tool correctly is missing.

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 four parameters (zip, page, radius, stock_type) are already documented in the schema. The description's 'new and used' phrasing loosely maps to stock_type but adds no format or default detail beyond what the schema supplies. Baseline 3 is appropriate.

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 opens with a specific verb+resource ('Search Cars.com vehicle listings') and specifies scope (new and used listings) plus what is returned. It is clearly a search tool, distinguishable from detail siblings like carsdotcom_vehicle, though it never names them explicitly.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as carsdotcom_vehicle for detail lookups or autotrader_search/carmax_search for other marketplaces. Usage is only implied by the verb 'Search'.

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