Find People Within Company
Give it a company domain, get back the people who work there.
- Tool
find_people_within_company- Cost
- 0.3 credits
- Category
- Person Search
- Required input
domain- Returns
- Profiles of people at that company
What it does
- Searches for people working at one specific company, identified by its website domain.
- Pulls from multiple providers, then merges and deduplicates the results into one list.
job_titlenarrows the list to the roles you care about — pass an array like["CTO", "VP Engineering"].- Returns 5 profiles by default, up to 50 per call via
max_profiles. - Cost is flat per call — 5 profiles and 50 profiles cost the same.
It returns profiles at one company. To search across many companies at once, use find_people instead — that tool takes role, size, location and education filters and costs 0.3 credits per result.
Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
domain | string | Yes | Company website domain |
job_title | array | No | Titles to match, e.g. ["CTO", "VP Engineering"] |
company_name | string | No | Helps disambiguate the company |
max_profiles | number | No | 1–50, default 5 |
How to use it
Connect the MCP server
Follow the setup guide for your client. Browser sign-in, no API key.
Ask for a role at a company
Find the CTO at stripe.comWiden the title list
Find people at stripe.com with the titles CTO, VP Engineering, or
Head of Platform. Return up to 20 profiles.Enrich the shortlist
For those profiles, find work emails and verify them. Do not guess
email patterns.Example prompts
| Ask your client | What you get back |
|---|---|
| ”Who is the CTO at stripe.com?” | A small set of matching profiles |
| ”Find 20 sales leaders at shopify.com” | Up to 20 profiles filtered by title |
| ”List people at acme.com — no title filter, max 10” | A general sample of the company’s staff |
| ”Find VP Sales at 50 different SaaS companies” | Better served by find_people — multi-company search |
Best prompting practices
- Pass the domain, not the company name. The domain is the required input and it is unambiguous.
company_nameis a supporting hint, not a substitute. - List title variants. “Head of Engineering” and “VP Engineering” are different strings. Pass both in the
job_titlearray. - Raise
max_profileson purpose. The default of 5 is small. The cost does not change when you ask for 50, so ask for the number you need in one call rather than repeating the call. - Say the company once per call. One domain per call — for a list of accounts, loop and cap the batch: “run this for these 20 domains and report credits used”.
- Search before you enrich. Confirm the profiles look right before spending credits on emails or phone numbers.
Output
{
"profiles": [
{
"name": "Jane Doe",
"title": "CTO",
"company": "Stripe",
"linkedin_url": "https://linkedin.com/in/janedoe"
}
]
}Credits and limits
0.3 credits per call, flat. max_profiles accepts 1–50 and defaults to 5. Run check_credits (free) before looping across a list of domains.
A narrow job_title array can return nothing if the company titles that role
differently. If a search comes back empty, retry without the title filter and
scan the full list before assuming the person does not exist.
Related tools
| Tool | Use it instead when |
|---|---|
find_people | You are searching many companies at once — 0.3 credits per result, full filter set |
newly_hired_executives | You only want recent hires, with new and previous role |
enrich_organization | You want firmographics on the company, not its people |
find_work_email | You already have the LinkedIn URLs and need contact details |
Next steps
- All MCP tools — the full catalogue with credit costs
- MCP use cases — account-based list building
- AI for Sales Reps — workflows that chain this tool into a list build
Keep learning
Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.