Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

autotrader_vehicle

Retrieve full Autotrader vehicle listing details by ID, including specs, pricing, images, description, and seller information.

Instructions

Get Autotrader vehicle listing detail. Returns an Autotrader vehicle listing: full vehicle spec (make, model, trim, mileage, colors, transmission, fuel type, engine, images, pricing), the full listing description, and seller detail (dealership or private seller).

Input Schema

NameRequiredDescriptionDefault
idYesAutotrader listing id, the numeric path segment of a /cars-for-sale/vehicle/{id} URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses the payload shape (spec, listing text, seller detail), but never states explicitly that this is a read-only, idempotent lookup or whether it needs auth/rate limits. 'Get' implies a read, which is reasonable but not explicit.

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?

Front-loaded with the core action in the first sentence; the second sentence efficiently enumerates the returned fields. The field list is long but arguably earns its place since no output schema exists.

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 endpoint with no output schema, the description adequately conveys what comes back (vehicle spec, description, seller). Missing only behavioral details like error handling or the read-only nature, which keeps it from a 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?

Single required parameter with 100% schema description coverage, including a precise explanation of the id format (numeric path segment of a /cars-for-sale/vehicle/{id} URL). The description adds nothing beyond the schema, 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?

States a specific verb and resource ('Get Autotrader vehicle listing detail') and names the data domain clearly. It is distinguishable from autotrader_search and autotrader_dealer by implication (this is a detail fetch by id), but the description never explicitly contrasts with those siblings.

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?

Usage is only implied: an agent infers it should call this when it already has a listing id, versus using autotrader_search to find one. There is no explicit when-to-use statement or named alternative, so a 3 is appropriate.

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