Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

autotrader_dealer

Fetch an Autotrader dealer profile—name, phone, address, rating, website—plus a first page of current inventory summaries and total listing count using the dealer ID.

Instructions

Get Autotrader dealer profile. Returns an Autotrader dealer profile (name, phone, address, rating, website) plus a first page of the dealer's own current inventory as vehicle summaries and the dealer's total listing count.

Input Schema

NameRequiredDescriptionDefault
idYesAutotrader dealer/owner id, the numeric path segment of a /car-dealers/{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?

No annotations, so the description carries the full burden. It usefully discloses the return payload (profile fields, a first page of inventory, total listing count) and hints at pagination via 'first page', but says nothing about auth requirements, rate limits, or how to fetch subsequent inventory pages.

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, front-loaded with the operation and resource, with the second sentence doing useful work by enumerating the payload. Slightly long but no wasted clauses.

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?

There is no output schema, so the description's enumeration of returned fields and the bundled inventory page correctly fills that gap for a one-parameter read tool. Only the pagination/auth behavior around the 'first page' of inventory remains unstated.

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% and the single id parameter is already well documented in the schema as the numeric path segment of a /car-dealers/{id} URL. The description adds no additional parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('Autotrader dealer profile'), then enumerates the returned fields and the bundled inventory page. An agent can distinguish it cleanly from autotrader_search (find listings) and autotrader_vehicle (single vehicle detail).

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?

No when-to-use guidance, no mention of when this is preferable to autotrader_search or autotrader_vehicle, and no note on where the dealer id comes from (a /car-dealers/{id} URL or a prior search). The purpose is implied but nothing routes the agent.

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