Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Google Maps B2B Email & Places Scraper

scrape_google_maps_leads
Read-onlyIdempotent

Extract local business leads from Google Maps with verified emails, phone numbers, social links, ratings, and reviews to build targeted B2B prospect lists.

Instructions

Extract local business leads from Google Maps including verified website emails (MX/SPF/DMARC), phone numbers, Instagram/LinkedIn/Facebook links, ad pixels, ratings, and reviews ($1.50/1k all-inclusive).

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": {
      "queries": "<queries>"
    },
    "name": "scrape_google_maps_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesSearch terms, e.g. ["dental clinic", "medspa", "roofing contractor"]
locationNoOptional city, state, or country filter, e.g. "Austin, TX, USA"
maxResultsPerQueryNoMaximum places per search query (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add context — and it does: it discloses that emails are validation-checked via MX/SPF/DMARC and that pricing is $1.50/1k all-inclusive, which is genuinely useful for cost-aware invocation. Remaining gaps are secondary: no mention of rate limits, deduplication across queries, or whether results are capped.

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 front-loaded sentence with the verb leading and the output inventory following; no filler or repetition. The trailing price parenthetical slightly dilutes the focus but is short and informative enough to earn its place.

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 carries the return-value burden and does so by enumerating the lead fields produced. For a three-parameter, well-documented read tool, that is close to sufficient; only result-volume/pagination behavior and cross-query dedup expectations are unaddressed.

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 three parameters (queries, location, maxResultsPerQuery) are already documented with examples and defaults. The description adds no parameter-level meaning beyond the schema, making the baseline of 3 appropriate.

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 ('Extract local business leads from Google Maps') and enumerates the payload fields returned (emails, phones, socials, pixels, ratings, reviews), which is concrete and unambiguous. It does not, however, distinguish itself from the many sibling lead-scraping tools (e.g. scrape_apollo_alternative_leads, find_dental_medical_clinic_leads), so an agent cannot route on purpose alone.

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 or when-not-to-use guidance, no stated prerequisites, and no named alternative. The only usage signal is the implicit example query list in the schema, which is structural rather than descriptive.

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