Skip to main content
Glama

Crawlora MCP

by net.crawlora.mcp
OverviewDiscussionsAdmin

datasets_vehicle_listings_search

Read-only

Search the used-vehicle listings dataset (crawled catalog: year/make/model/trim, mileage, price, seller and location; CarMax's national inventory plus a zip-swept, best-effort Autotrader/Cars.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoOptional full-text query over make, model and trim, max 256 characters.
vinNoOptional exact VIN filter. VIN is present on a best-effort basis and not guaranteed on every listing.
makeNoOptional exact make filter (e.g. Honda, Toyota), max 128 characters.
pageNoResult page number, 1-based, default 1; page times page_size must not exceed 10000.
sortNoOptional sort order. Allowed values: relevance, recently_updated, newly_listed, price_asc, price_desc, mileage_asc, mileage_desc, year_desc, year_asc. Defaults to relevance with q, otherwise recently_updated.
trimNoOptional exact trim filter, max 128 characters.
modelNoOptional exact model filter (e.g. Civic), max 128 characters.
stateNoOptional exact US state abbreviation filter (e.g. CA), max 8 characters.
run_idNoOptional exact crawl run-id filter, max 128 characters.
sourceNoOptional exact source marketplace filter. Allowed values: carmax, autotrader, carsdotcom.
max_yearNoOptional maximum model year, e.g. 2024.
min_yearNoOptional minimum model year, e.g. 2018.
fuel_typeNoOptional exact fuel type filter (e.g. Gas, Hybrid, Electric), max 128 characters.
max_priceNoOptional maximum price in US dollars, 0 or greater.
min_priceNoOptional minimum price in US dollars, 0 or greater.
page_sizeNoPage size, default 20, max 100; page times page_size must not exceed 10000.
body_styleNoOptional exact body style filter (e.g. Sedan, SUV), max 128 characters.
drive_typeNoOptional exact drivetrain filter (e.g. Front Wheel Drive), max 128 characters.
max_mileageNoOptional maximum odometer mileage, 0 or greater.
seller_typeNoOptional exact seller type filter. Allowed values: retailer, dealer, private.
transmissionNoOptional exact transmission filter, max 128 characters.
is_price_reducedNoOptional filter for listings currently marked down from a previous price.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful provenance context beyond the annotations: the data is a crawled catalog, coverage is 'best-effort' (especially Autotrader/Cars.com) and CarMax inventory is national, which signals completeness caveats an agent 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.

Conciseness4/5

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

A single dense sentence, front-loaded with the verb and resource, then qualifying the data sources. Nothing is wasted, though the parenthetical is slightly packed with caveats.

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?

With an output schema present and 100% schema coverage, the description needn't cover return values or parameter syntax. It supplies the dataset scope and provenance needed to call the tool correctly; only sibling disambiguation 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 22 parameters are already documented in the schema with defaults, enums and constraints. The description adds no per-parameter meaning 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 (Search) and resource (used-vehicle listings dataset) and enumerates the crawled fields (year/make/model/trim, mileage, price, seller, location). It does not differentiate itself from its close siblings (datasets_vehicle_listings_facets, _item, _price_history), so it falls short of 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 and no mention of alternatives. It never tells the agent when to reach for datasets_vehicle_listings_facets, _item, or _price_history instead, nor when to prefer the live carmax/autotrader/carsdotcom sibling tools. 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.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources