Lead Finder: search the contact database (free)
search_lead_finderSearches Emailchaser's B2B contact database (Lead Finder) with explicit filters and returns one page of matching people, masked: first name, last initial, title, seniority, job function, company name, industry, size and revenue band, and location. Email addresses, domains, LinkedIn URLs and phone numbers are never shown; contact details are revealed only when people are added to a campaign. Spends no credits, but every result row uses the account's daily browsing allowance (rowsLeftToday; 2,000 rows a day by default, 250 on a trial). An account may start 20 searches a minute. Searches that find nobody also draw on a bucket of 120 that refills one every 30 seconds; while it is empty every new search is refused for a moment (rate_limited, reason empty_searches, with retryAfterSeconds). The same page asked for again within 10 minutes costs nothing. total is the exact audience size only when totalIsExact is true; otherwise it is a lower bound (often 50,000). If status is running or totalStatus is pending, total, hasMore and maxPage are recomputed when the search is read again by its searchId. The exact count is fetched in the background and can take up to about a minute, so totalStatus can read pending (and totalIsExact false) on several polls in a row: that is normal, not an error. The count is settled once totalIsExact is true or totalStatus is done (exact) or failed (the count could not be fetched, so total stays a lower bound); each read of the search waits about six seconds, so around ten reads cover it. The people already returned are final and usable the whole time: show them, and add them with their refs, without waiting for the count. status failed means the search did not run, and error says why (rate_limited, timeout, provider_blocked, budget_exhausted, invalid_filters, expired or internal): it is not an empty audience, so try again later. Each result's ref identifies that person when adding them to a campaign, valid for 60 minutes after its page was last shown. inWorkspace means Lead Finder added that person to this workspace and their lead is still there, so adding them again is skipped for free; someone who is a lead from another source shows false, and adding them is skipped for free too. A read-only key may use this tool.
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": {
"filters": "<filters>"
},
"name": "search_lead_finder"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Results page, starting at 1 (default 1). The deepest page is 100 by default, and a search's maxPage says how deep that audience goes | |
| filters | Yes | Who to look for. Every field is optional but at least one include filter is required. Free-text fields take up to 50 values of up to 100 characters each (get_lead_finder_filters has the limits that apply); a value with commas is split into one value per comma, and blank values are ignored. A filter the API cannot use is refused with the field, value and reason named. | |
| pageSize | No | People per page: 25 (default) or 50 |