Skip to main content
Glama

Google Maps No Website Leads: Businesses With No Website $3/1k

find_local_businesses_without_website
Read-only

Find local businesses without a website or with only social pages, returning phone, address, rating, and lead score for outreach.

Instructions

Local businesses on Google Maps with no website of their own (or only a Facebook, Instagram or booking page), for any trade and town: name, phone, address, rating, review count, website status, a lead score and a factual opening line. Domains matching each name are tested, so businesses that do have a site are set aside; in France and the UK the registered company is matched. Only the leads found are charged, never the places read. Pay per result on your Apify account: run start $0.003, no-website lead $0.003, place with a website $0.001.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_local_businesses_without_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoTwo-letter language code (en, fr, de, es, it…).
maxLeadsNoThe run stops when this many leads are saved. You pay per lead saved, never for the places that were read and set aside. Default here: 25.
radiusKmNoKeep only the places within this distance of the location: a typed "lat,lon" point ("53.80,-1.55"), or the location found on OpenStreetMap (a neighbourhood, a street, a town). Places farther away are skipped for free, and each lead gets distanceKm. Places with no address are never judged. Empty = the whole area Google Maps returns.
searchesNoWhat you would type in Google Maps: a trade or a kind of shop (plumber, hair salon, restaurant, garage, dentist…). One search per line. Write it in the language of the country for more results ("plombier" in France, "Friseur" in Germany).
locationsNoCities, districts or postcodes. Each business type is searched in each location. Google Maps shows about 100 to 120 places per search: for a large city, add its districts or neighbouring towns as separate lines to go deeper.
minRatingNoKeep only businesses rated at least this, e.g. "4" or "4.5" (happy customers, a business worth a good website). Places without any rating are skipped when this is set.
minReviewsNoKeep only businesses with at least this many reviews (an active business with customers). 0 keeps all.
countryCodeNoOptional two-letter country code (fr, gb, us, de…): tells Google where to look when a city name exists in several countries. Not needed when the location already names the country.
onlyUnclaimedNoKeep only businesses whose Google Business Profile has not been claimed by its owner (Google Maps shows "Claim this business"). These owners have never set up their listing: a second thing to offer them besides a website. Skipped places are free.
onlyWithPhoneNoSkip listings without a phone number.
maxPlacesPerSearchNoHow many Google Maps places to read for each business type in each location (20 per page). Reading is free: only the leads are charged. Default here: 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the core internal behavior: candidate domains are tested per business name, set-aside places are free, and France/UK runs match the registered company. It also gives a full cost breakdown by event type, which is exactly the kind of charge-risk context annotations cannot convey. Not a 5 only because run duration and result-count caps are left to the schema.

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?

The lead definition comes first, the dedup/verification logic second, and the pricing last, with no filler sentences. The pricing clause is dense but every element (run start, lead, rejected place) matters for a paid tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, zero-required, paid scraping tool with no output schema, the description covers what is returned (name, phone, address, rating, review count, website status, lead score, opening line), how verification works, and exactly what is billed. There is no output schema, and the description compensates by enumerating the result fields.

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 parameter docs are unusually rich (defaults, free-vs-charged semantics, per-location logic), so the description adds little parameter-level meaning on its own. Its only extra signal is that names are used as domain probes, which explains why false negatives are possible.

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 resource and filter: local businesses on Google Maps that lack their own website (or only have a Facebook/Instagram/booking page), and it lists the fields returned. It is easy to distinguish from the local-business sibling that targets registered companies, but it never names that alternative, so differentiation is inferred from wording rather than stated.

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 framing (lead scoring, opening line, no website) makes the lead-generation use case obvious, and the schema carries practical hints like writing searches in the local language and splitting large cities into districts. There is no explicit when-to-use / when-not-to-use statement or named alternative tool.

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