Filters and contact fields

Call get_search_filters before building a search. It returns the current JSON schema, suggestions, and an example. Suggested values are not exhaustive. The same filters object works with preview_leads, get_search_count, and search_leads.

All supported filters

Field	Type	Purpose
first_name	string	First name
last_name	string	Last name
job_titles	string array	Job titles
job_title_seniority	string array	Seniority levels
job_departments	string array	Departments
employee_size	string array	Company employee ranges
company_revenue	string array	Company revenue ranges
person_location_country	string array	Person's country
person_location_region	string array	Person's state or region
person_location_locality	string array	Person's city or locality
industries	string array	Company industries
industry_keywords	string array	Industry keywords
inferred_salary	string array	Salary ranges
funding_start_date	ISO date string	Funding period start, YYYY-MM-DD
funding_end_date	ISO date string	Funding period end, YYYY-MM-DD
business_model	string array	Business models
company_location_country	string array	Company country
company_location_region	string array	Company state or region
company_location_locality	string array	Company city or locality
company_websites	string array	Company websites
email_status	enum	all, verified, or likely
include_emails	boolean	Include email data
include_phones	boolean	Include phone data
max_results	integer	Paid-search cap, 1–100,000; does not cap the total preview count

All filter fields are optional. Arrays accept up to 100 values; text values must be nonempty and at most 500 characters. Unknown fields are rejected. Use the explicit top-level max_results argument to set the paid search budget for search_leads; it takes precedence over the value inside filters.

MCP pagination is passed as tool arguments, not _page or _per_page in filters. REST-only fields such as _include_raw are not accepted in the MCP filter object.

Example: preview before searching

Arguments for preview_leads:

{
  "filters": {
    "job_titles": ["Founder", "CEO"],
    "person_location_country": ["United States"],
    "employee_size": ["11-50", "51-200"],
    "include_emails": true,
    "email_status": "verified"
  },
  "page": 1,
  "limit": 25
}

Preview responses mask contact details and spend no credits. Use get_search_count with the same filters to check match volume. Respect its count_exact / estimated indicators when reporting totals.

Preserve every returned field

get_search_results returns rows containing position and lead_payload. The payload contains all fields returned for that search. Do not reduce it to only name and email when saving results: use save_search_results to preserve the complete payload in the saved contact's lead_data.

For manually supplied contacts, add_leads_to_list and update_saved_lead support:

Field	Type / maximum length
full_name, email, job_title, company_name, industry	Nullable string, 500 characters
phone, company_size	Nullable string, 100 characters
linkedin_url	Nullable string, 2,000 characters
location	Nullable string, 1,000 characters
source	String, 100 characters
lead_data	JSON object for all additional fields

JSON exports retain the saved contact and lead_data. CSV exports include lead_data as a JSON-encoded cell alongside the standard columns. Not every source record has every field populated.