Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

carsdotcom_vehicle

Retrieve full details for a Cars.com vehicle listing by its listing ID, including specs, pricing, history, dealer info, and features.

Instructions

Get Cars.com vehicle listing detail. Returns a Cars.com vehicle listing: full vehicle spec (make, model, trim, mileage, colors, engine, transmission, fuel economy, a key-specs table), Cars.com's own deal-fairness rating and predicted fair price, categorized equipment features, an AutoCheck-derived vehicle history report, Cars.com's own price-change history, the seller's notes, dealer detail (name, rating, address, website, phones, hours) or private-seller detail for a for-sale-by-owner listing, and certified-pre-owned/manufacturer-program detail when applicable.

Input Schema

NameRequiredDescriptionDefault
listing_idYesCars.com listing id (a UUID), the path segment of a /vehicledetail/{listing_id}/ URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does substantial work: the read verb 'Get' plus 'Returns a ... listing' makes the non-destructive, idempotent nature clear, and the payload is enumerated field-by-field, which is valuable given there is no output schema. It stops short of 5 because it says nothing about failure modes for an invalid/expired listing id, auth requirements, or rate limits.

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?

Purposely front-loaded: a one-line purpose sentence followed by the return inventory. The return sentence is long and comma-listed, but since no output schema exists, the enumeration earns its space rather than being filler.

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 one-parameter detail-fetch tool with no output schema, the description fully covers what comes back, which is the main completeness risk. The remaining gap is procedural (how to obtain a valid listing_id, what happens on a bad id), which keeps it below 5.

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?

There is a single parameter with 100% schema description coverage; the schema already explains it is a Cars.com UUID matching the /vehicledetail/{listing_id}/ path segment. The description adds no additional meaning about the parameter, so the baseline 3 applies.

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 ('Get Cars.com vehicle listing detail') and enumerates the returned payload in detail, so an agent knows exactly what the tool fetches. It never names the sibling carsdotcom_search or otherwise explicitly separates itself from listing-search tools, which keeps it from a 5.

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 statement that listing_id must come from carsdotcom_search, and no exclusions (e.g., this is a single-listing fetch, not a search). The agent must infer the usage pattern from the parameter name alone.

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