Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

carsdotcom_search

Search Cars.com vehicle listings by ZIP code, radius, page, and condition to retrieve normalized car details—make, model, year, mileage, price, seller, images—and total matches.

Instructions

Search Cars.com vehicle listings. Searches Cars.com for new and used car listings, returning normalized vehicle summaries (make, model, trim, year, mileage, exterior color, drivetrain, fuel type, pricing, seller, images) plus the total matching count. Credential-free public data sourced directly from Cars.com's own public search API.

Input Schema

TableJSON 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

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 the full burden. It usefully discloses that the data is 'Credential-free public data sourced directly from Cars.com's own public search API', signaling no auth setup and a legitimate public source, and it summarizes the output structure. It does not cover pagination or no-parameter behavior, but the core traits are disclosed.

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 is compact but the first two sentences are somewhat redundant ('Search Cars.com vehicle listings' vs 'Searches Cars.com for new and used car listings'). The field list and credential-free note earn their place, but the opening repetition wastes a sentence.

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 no output schema, the description compensates well by listing the normalized vehicle summary fields and the total matching count. It does not mention behavior with zero parameters or pagination, but the schema and output list cover most of what an agent needs.

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?

The input schema already describes all four parameters (zip, page, radius, stock_type), including the 24-per-page default and enum values, so the description adds little. It does not add format or dependency details beyond the schema, so 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 states a specific verb ('Searches') and resource ('Cars.com for new and used car listings'), and enumerates the returned fields. It is clear what the tool does, though it does not explicitly contrast with the sibling carsdotcom_vehicle, leaving the distinction to inference.

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 makes the use case clear ('Search Cars.com vehicle listings'), but it never says when to prefer this tool over alternatives like autotrader_search or carsdotcom_vehicle, nor when not to use it. Guidance is implied rather than explicit.

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