Pullwire

Google Maps Leads Scraper

maps-leads

Read-only

Find businesses on Google Maps by type and location (optionally within a radius): name, address, phone, website, rating, reviews, categories and opening hours, plus emails (with the page they were found on), phone numbers and social profiles from each business website. One row per company. No login, no browser. Costs 1 credit per result; failed items are free.

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": {
      "searches": "<searches>"
    },
    "name": "maps-leads"
  }
}

Input Schema

Name	Required	Description	Default
`dedupe`	No	Return each business only once even when several searches find it.
`language`	No	Language of categories, opening hours and descriptions, e.g. "en", "de", "fr".	en
`searches`	Yes	One entry per business type + location combination.
`maxResults`	No	Stop after this many businesses in total across all searches. Empty: no extra cap.
`countryCode`	No	Two-letter country code that biases ambiguous place names, e.g. "us" or "de". Empty: none.
`onePerCompany`	No	Skip a business whose website domain or phone number was already returned (branches of one company, double listings). Shared hosts like Facebook pages or booking platforms never count as the same company.
`enrichContacts`	No	Visit each business website (homepage plus contact, imprint or privacy pages when needed) to collect email addresses, phone numbers and Facebook, Instagram, LinkedIn, X, YouTube, TikTok and Pinterest profiles.
`maxContactPages`	No	Homepage plus up to this many minus one contact, imprint or privacy pages, only while no address of the business itself has been found (an agency or platform address alone does not count).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower, and the description still adds real behavior: no login or browser required, a per-result credit cost, free failures, and one row per company with emails traced to their source page. It stops short of discussing runtime, rate limits, or partial-result behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, front-loaded with the core capability, then the enumerated outputs and the cost/constraint facts. Every clause carries information an agent needs; nothing is padding.

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 an eight-parameter tool with no output schema, the description compensates well by listing the result fields an agent will receive, plus cost and login-free operation. Remaining gaps are minor: it doesn't mention result caps or what happens when a search yields nothing.

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 parameter meaning is already fully documented in the schema, including dedupe, radius and contact-page limits. The description adds only the 'optionally within a radius' hint and the note that emails come with the page they were found on, which is marginal beyond the schema.

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 states a specific verb and resource ('Find businesses on Google Maps by type and location') and enumerates the returned fields, so an agent knows exactly what the tool produces. It does not explicitly distinguish itself from adjacent siblings such as website-contacts, whose email-extraction role overlaps with the enrichment part described here.

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 implied by the lead-generation framing and by the cost model ('1 credit per result; failed items are free'), which signals when this is worth calling. There is no explicit when-to-use/when-not guidance and no named alternative for cases like pure contact lookup or general web search.

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

All Pullwire tools Inspect

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

Need Help?