Search local-business leads
search_leadsRun a live search for local businesses by niche + city (e.g. query 'electrician', location 'Austin, TX'). Returns a search_id and, usually, the first batch immediately (its listings are in results; their emails and phones are not verified yet — when discovery is 'in_progress' the provider was slow and the whole search was queued, so the leads arrive through get_search_results); more results are found and verified in the background — every email is SMTP-checked and phones are verified with line type + carrier. Spends 1 lead per result. Poll get_search_results until enrichment is 'complete'. If enrichment is already 'complete', nothing was found and nothing more is coming; if capped is true, the balance covered fewer leads than were found. With country, a US territory (PR, GU, VI, AS, MP) is searched; max_leads stops it early and exact_category keeps only that Google category. For many keywords or places at once, use run_advanced_search.
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": {
"query": "<query>"
},
"name": "search_leads"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Business niche/category keyword, e.g. 'electrician'. | |
| country | No | 'US' (the default), or a US territory's code ('PR', 'GU', 'VI', 'AS', 'MP') with a place from find_places. | |
| location | No | City, e.g. 'Austin, TX'. Not needed with location_code, which is always what is searched. | |
| max_leads | No | Stop after this many leads: a whole number from 100 to 1,000,000. | |
| location_code | No | Optional exact location code. When given, it is what is searched, whatever location says. Sent with location, the search is named after the code's own place (or after location when the code's own name cannot be looked up); sent alone, the search is unnamed and location comes back null. A code for a place outside the US is refused, as is a location ending in another country ('London, UK'). | |
| exact_category | No | Only businesses whose MAIN Google category is the query's: true (the query must be a Google category, e.g. 'Plumber'), or the category's id. Runs in the background — results arrive through get_search_results. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| found | No | Listings found in the first batch, before the balance capped delivery. | |
| query | Yes | ||
| capped | No | True when the lead balance covered fewer leads than were found — relay this to the user. | |
| results | No | The first batch, as delivered — contacts are verified in the background (get_search_results). | |
| location | No | The place searched, as the location list names it (the location sent, when a code's own name could not be looked up); null for a location_code sent alone. | |
| discovery | No | 'complete', or 'in_progress' when the search was queued whole. | |
| next_step | No | ||
| search_id | Yes | ||
| enrichment | Yes | 'pending' until background verification finishes; 'complete' at once when nothing was found. | |
| data_sources | No | Where the sources, licences and notices are for emails and owner names that may come from open datasets and public records. Pass it on with any of this data you share. | |
| leads_remaining | No | Leads spendable now. On a plan with no monthly quota this is what is left in the current 7-day period. Null when that period's usage couldn't be read just then — ask again. | |
| delivered_so_far | Yes |