Check Promotions
Give it a LinkedIn profile URL, find out whether that person has recently been promoted.
- Tool
check_promotions- Cost
- 2 credits
- Category
- Person Signals
- Required input
profile_url- Returns
- Recent promotion signal
What it does
- Checks one LinkedIn profile for a recent promotion. A bare username works in place of the full URL.
- Answers a single question — did this person move up — without pulling their whole history.
- One profile per call, flat cost.
A promotion is different from a job change. The person stayed at the company; what changed is their scope and, usually, their budget. That makes it a strong expansion signal on existing accounts and a re-qualification trigger on stalled ones.
For a move to a different company, use check_job_change.
Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
profile_url | string | Yes | LinkedIn URL or username |
How to use it
Connect the MCP server
Follow the setup guide for your client. Browser sign-in, no API key.
Check one person
Has linkedin.com/in/janedoe been promoted recently?Sweep an account list
Check these 40 LinkedIn URLs for recent promotions. Return only the
people who were promoted, with their new title. Report credits used.Act on the signal
For everyone promoted, draft a three-line note about what their new
scope changes — not a congratulations message.Example prompts
| Ask your client | What you get back |
|---|---|
| ”Was this person promoted?” | A yes or no signal for one profile |
| ”Check these 40 contacts and list only the promotions” | A filtered list with new titles |
| ”Which contacts at our open opportunities moved up this quarter?” | Expansion signals across an account list |
| ”Did they leave the company?” | Better served by check_job_change — a different signal |
Best prompting practices
- Say “promoted”. “New role” is ambiguous and may route your client to
check_job_change, which is a different signal at the same price. - Ask for promotions only. Filtering in the prompt saves you from reading 40 rows to find 4.
- Deduplicate before the run. At 2 credits each, duplicates are expensive.
- Cap the batch. “Stop after 50 and report credits used.”
- Re-check on a schedule, not on a loop. Promotions are quarterly-scale events. Weekly re-runs cost credits and return the same answer.
- Skip the congratulations. Everyone sends those. Lead with what their new scope makes possible instead.
Output
{
"profile_url": "https://linkedin.com/in/janedoe",
"promotion": true,
"new_title": "SVP Revenue",
"company": "Stripe"
}Credits and limits
2 credits per check, flat. Run check_credits (free) before sweeping a large list.
The signal depends on the person updating their own LinkedIn profile. Internal title changes are often posted late or not at all, so a negative result means “nothing detected” rather than “no promotion happened”.
Related tools
| Tool | Use it instead when |
|---|---|
check_job_change | They moved to a different company — 2 credits |
newly_hired_executives | You are watching a company for incoming leadership — 0.5 credits per profile |
linkedin_profile_enrich | You want the full title history, not just the change — 1 credit |
enrich_person | You need the current contact record refreshed |
Next steps
- All MCP tools — the full catalogue with credit costs
- MCP use cases — signal-triggered outreach workflows
- Signals & ABM — workflows that chain this tool into a play
Keep learning
Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.