Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

CarGurus & Auto Dealership Leads, Inventory & Contacts

scrape_cargurus_auto_dealer_leads
Read-onlyIdempotent

Extract auto dealership leads by city/state with verified emails, phone numbers, addresses, dealer websites, CarGurus profiles, and automotive CRM/DMS software data.

Instructions

Extract auto dealerships by city/state with official dealer websites, CarGurus profile links, verified dealership emails, phone numbers, addresses, and automotive CRM/DMS software stack ($0.75/1k).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locations": "<locations>"
    },
    "name": "scrape_cargurus_auto_dealer_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationsYesTarget cities and states, e.g. ["Austin, TX", "Dallas, TX"]
maxDealersNoMaximum dealership leads

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description's one genuine addition is the '$0.75/1k' pricing signal, which is real context for a metered scrape. It says nothing about result caps, runtime, verification methodology for 'verified' emails, or what happens when a location yields no dealers.

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 sentence that front-loads the verb and target and packs the field list and price into the same breath, with no filler. The dense trailing field enumeration is slightly hard to parse but earns its place since there is no output schema.

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 no output schema, the description usefully enumerates the return fields, which is exactly what an agent needs to judge result fit. For a two-parameter, fully-documented schema with strong safety annotations, the missing pieces (usage routing, per-call limits) are minor rather than blocking.

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 schema already gives an example for locations and the default of 15 for maxDealers. The description adds no parameter-level detail beyond the schema, so baseline 3 applies. The '$0.75/1k' note indirectly hints that cost scales with lead count, but that's not parameter guidance.

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 names a specific verb (extract) and resource (auto dealerships by city/state) and enumerates the concrete fields returned: websites, CarGurus profile links, emails, phones, addresses, and CRM/DMS stack. It's clearly distinguishable as the automotive-vertical lead scraper among the lead-gen siblings, though it doesn't name an alternative to contrast against.

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: the automotive framing makes it obvious this is the tool for dealer lead lists, and the '$0.75/1k' hint signals a cost-aware bulk use case. There is no explicit when-to-use vs when-not guidance or steer toward/away from sibling lead scrapers such as the Google Maps or Apollo alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.