Count Matching People by Job, Company, or Location | ContactOut
Count ContactOut profiles matching a job title, company, skill, or location. See the total and estimated counts for possible email or phone details; no names or contact details are returned.
Free
ContactOut
Count Matching People by Job, Company, or Location | ContactOut
Count ContactOut profiles matching a job title, company, skill, or location. See the total and estimated counts for possible email or phone details; no names or contact details are returned.
You receive
Count the people in ContactOut who match your description. The result also estimates how many may have a work email, personal email, or phone number.
Start with your task
Count how many people in ContactOut match [job title] at [company name] in [city or region]. Also estimate how many may have a work email, a personal email, or a phone number.
What to know
Email and phone counts are estimates. This Tool returns counts only—not names, individual profile pages, or actual contact details.
Inputs & outputs
Inspect the current inputs, availability, and maximum charge before starting.
Input schema
Input schema
Field / Path
Type
Requirement
Meaning
bodybody
object
Optional
namebody.name
string
Optional
Name of the person.
Minimum length
1
domainbody.domain
array
Optional
Company domains.
Maximum items
50
[]body.domain[]
string
—
Minimum length
1
skillsbody.skills
array
Optional
Skills to match. Supports boolean equations.
Maximum items
50
[]body.skills[]
string
—
Minimum length
1
companybody.company
array
Optional
Company names.
Maximum items
50
[]body.company[]
string
—
Minimum length
1
keywordbody.keyword
string
Optional
Keyword matched anywhere in the profile. Supports boolean equations.
Minimum length
1
industrybody.industry
array
Optional
Industries (LinkedIn vocabulary, e.g. 'Computer Software'). Prefix a value with NOT to exclude it.
Maximum items
50
[]body.industry[]
string
—
Minimum length
1
locationbody.location
array
Optional
Locations of the person.
Maximum items
50
[]body.location[]
string
—
Minimum length
1
educationbody.education
array
Optional
Schools or degrees. Supports boolean equations.
Maximum items
50
[]body.education[]
string
—
Minimum length
1
job_titlebody.job_title
array
Optional
Job titles to match (any one). Supports boolean equations with capitalized AND/OR/NOT, e.g. '(CTO OR VP Engineering) NOT consultant'.
Maximum items
50
[]body.job_title[]
string
—
Minimum length
1
languagesbody.languages
array
Optional
Language requirements, each optionally narrowed by proficiency.
body.job_title · array · optional Job titles to match (any one). Supports boolean equations with capitalized AND/OR/NOT, e.g. '(CTO OR VP Engineering) NOT consultant'. {"maxItems": 50}
body.languages · array · optional Language requirements, each optionally narrowed by proficiency. {"maxItems": 50}
body.job_function · array · optional Functional areas, e.g. Engineering, Sales, Finance, Marketing, Human Resources, Product Management, Operations. {"maxItems": 50}
body.past_company · array · optional Companies from past (non-current) roles. {"maxItems": 50}
body.company_filter · string · optional How company names match: current employer (default), any past employer, past only, or both. {"enum": ["current", "past", "past_only", "both"]}
body.past_job_title · array · optional Job titles held in past (non-current) roles. Supports boolean equations. {"maxItems": 50}
body.location_radius · integer · optional Search radius in miles around the given location (city/area only). {"minimum": 1, "maximum": 500}
body.match_experience · string · optional Require job_title and company to match within the SAME experience entry. Cannot be combined with current_titles_only or company_filter. {"enum": ["current", "past", "both"]}
body.exclude_companies · array · optional Company names to exclude from results. {"maxItems": 50}
body.exclude_job_titles · array · optional Job titles to exclude from results. {"maxItems": 50}
body.past_work_location · array · optional Cities or countries where the person previously worked. {"maxItems": 50}
body.current_titles_only · boolean · optional Default true — match current job titles only; false also matches past titles.
body.years_of_experience · array · optional No endpoint-specific meaning or additional controls are documented for this field.
body.current_company_only · boolean · optional Default true — match the current company only.
body.is_currently_working · boolean · optional true → only profiles with an active current role; false → only profiles without one; omit for both.
body.current_work_location · array · optional Cities or countries where the person currently works. {"maxItems": 50}
body.recently_changed_jobs · boolean · optional true → only profiles whose current job started within the last 3 months. Cannot be combined with years_in_current_role.
body.years_in_current_role · array · optional Cannot be combined with recently_changed_jobs.
body.exclude_companies_filter · string · optional Where the exclusion applies: current employer, past roles, or both (default). {"enum": ["current", "past", "both"]}
body.include_related_job_titles · boolean · optional Include profiles with related job titles. Default false.
Returned data
Estimate the size of a people search before retrieving contact records.
The dated saved response demonstrates this Tool's returned structure. It describes one completed request, rather than guaranteed fields or coverage for every request.
The response estimates matching profile and contact coverage. A count is not a list of people or their contact details, and estimated coverage should remain labeled as an estimate.
Field reference
The keys below are observed in the saved response. Supporting and unexpected fields remain accessible in the result details and Raw JSON. An undocumented unit or scale stays in its original form.
status_code result.status_code — Present in the saved response. Its exact definition, unit and conditions are not established by the current output contract; retain the original value.
Matching profiles result.total_results — The reported number of matching profiles for this query, rather than a returned contact list.
Estimated phone coverage result.estimated_phones — Estimated phone coverage among matching profiles; retain the estimate label and do not treat it as a retrieved count.
Estimated work-email coverage result.estimated_work_emails — Estimated work-email coverage for the query, not verified deliverable addresses.
Estimated personal-email coverage result.estimated_personal_emails — Estimated personal-email coverage for the query, not a list of personal addresses.
Source and freshness
Saved Example: run completed 2026-10-01 15:30:03 PDT (US Pacific, America/Los_Angeles). This is run completion, not a publisher update time. Opening the Example does not execute the Tool.
Confirmed absolute result times are displayed in US Pacific time with the applicable PST/PDT. Relative, date-only and unknown-offset source dates retain their original meaning.
The executable inputs and current ceiling come from this exact Tool's contract. Supplier links provide source context; supplier-wide features do not expand this Tool's capability.
Copy the request into the AI assistant you already use. If you have not connected Toolmu yet, follow the setup guide. Copying the request does not start a search.
Tell your assistant which group you want to count. Start with one detail, such as [job title], [company name], or [city or region]. If the request could describe more than one group, ask your assistant to check with you before searching.
Count how many people in ContactOut match [job title] at [company name] in [city or region]. Also estimate how many may have a work email, a personal email, or a phone number.
Understand the result
You will see how many people match your description and estimates of how many may have work emails, personal emails, or phone numbers. These email and phone counts are estimates; names and actual contact details are not included.
Questions about this tool.
Inputs, results and details to know before running it.
No. It returns the total number of matching profiles and estimated counts of profiles that may include email or phone details. It does not return names, profile pages, or actual contact details.
Describe the group with at least one detail, such as [job title], [company name], or [city or region]. You do not need to provide a link to one specific person.
No. They estimate how many matching profiles may include those details. The total matching-profile count is shown separately.
Check the price shown on this page before you start; it can change.
No. It is a saved result from an earlier run, not a new search. Start a new task to get a count for your own criteria.
