Enrich Person
Give it whatever you know about a person, get back the fuller record.
- Tool
enrich_person- Cost
- 1 credit
- Category
- Person Enrichment
- Required input
- At least one identifier
- Returns
- Contact details, job title, company info
What it does
- Enriches a person from any identifier — first name, last name, email, LinkedIn URL or organization name.
- Returns contact details, job title, company info, and more.
- You must pass at least one identifier. Every extra identifier you pass narrows the match.
- One call, one credit, however many identifiers you send.
It is the general-purpose person lookup. If you have a LinkedIn URL and you want full profile detail — work history, education, skills — use linkedin_profile_enrich instead.
Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
first_name | string | At least one | Pair with last_name |
last_name | string | At least one | Pair with first_name |
email | string | At least one | Any known address |
linkedin_url | string | At least one | LinkedIn profile URL |
organization_name | string | At least one | Company name |
Any identifier you do not use as the anchor is optional — pass it anyway to disambiguate.
How to use it
Connect the MCP server
Follow the setup guide for your client. Browser sign-in, no API key.
Enrich from a name and company
Enrich Jane Doe at StripeEnrich from an email
Enrich the person behind jane@stripe.comEnrich a list
Enrich these 30 rows. Each has a first name, last name and company. Report how
many credits you used and which rows came back empty.Example prompts
| Ask your client | What you get back |
|---|---|
| ”Enrich Jane Doe at Stripe” | Title, company and contact details |
| ”Who is jane@stripe.com?” | The person record behind the address |
| ”Enrich linkedin.com/in/janedoe” | The person record from the profile URL |
| ”Enrich this CSV of names and companies” | One record per row, empties flagged |
Best prompting practices
- Always pass the company. A name on its own matches the wrong Jane Doe more often than you would like.
organization_nameis free and it fixes most of those. - Anchor on the strongest identifier you have. Email and LinkedIn URL beat a name.
- Say what you want back. “Just the job title and company” keeps the client from dumping the whole record into the chat.
- Cap the batch. “Stop after 50 and report credits used” keeps a long list from running away with your balance.
- Ask for the profile tool by name when you want work history or education — otherwise your client will settle for this one and give you a thinner record.
Output
{
"first_name": "Jane",
"last_name": "Doe",
"job_title": "VP Sales",
"email": "jane@stripe.com",
"organization_name": "Stripe"
}Credits and limits
1 credit per call. Run check_credits (free) before a large batch.
A common name with no company attached can resolve to the wrong person, and a
wrong match still costs a credit. Pass organization_name or linkedin_url
whenever you have one, and spot-check the first few rows of any batch before
you let it run to the end.
Related tools
| Tool | Use it instead when |
|---|---|
linkedin_profile_enrich | You have a LinkedIn URL and want work history, education and skills — 1 credit |
find_work_email | You only need the work email — 1 credit |
find_people | You cannot name the person yet and need to search — 0.3 credits per result |
enrich_organization | You want the company record, not the person — 2 credits |
Next steps
- All MCP tools — the full catalogue with credit costs
- 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.