Skip to Content
MCPToolsCheck Job Change

Check Job Change

Give it a LinkedIn profile URL, find out whether that person has recently changed jobs.

Tool
check_job_change
Cost
2 credits
Category
Person Signals
Required input
profile_url
Returns
Recent job-change signal

What it does

  • Checks one LinkedIn profile for a recent job change. A bare username works in place of the full URL.
  • Answers a single question — did this person move — so it is cheaper to read and act on than a full profile enrich.
  • One profile per call, flat cost.

Two common uses:

  • Timing. A new hire in their first 90 days is buying, rebuilding and replacing tools. This is the window.
  • Hygiene. A champion who left means the contact record in your CRM is dead and the account may be at risk.

For a promotion rather than a move, use check_promotions.


Parameters

ParameterTypeRequiredNotes
profile_urlstringYesLinkedIn 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 changed jobs recently?

Sweep your closed-won list

Check these 60 LinkedIn URLs for recent job changes. Return only the people who moved, with their new company. Report credits used.

Act on the movers

For everyone who moved, pull their new work email and draft a three-line note referencing the new role.

Example prompts

Ask your clientWhat you get back
”Did this person change jobs?”A yes or no signal for one profile
”Check these 60 URLs and list only the movers”A filtered list of people who changed company
”Which of our champions left their company?”Churn-risk accounts surfaced from a customer list
”Were they promoted?”Better served by check_promotions — a different signal

Best prompting practices

  • Say “changed jobs”. “Got a new role” is ambiguous — it may route your client to check_promotions, which is a different signal at the same price.
  • Ask for movers only. “Return only the people who moved” cuts a 60-row report down to the rows you will act on.
  • Deduplicate before the run. At 2 credits each, duplicate URLs are expensive.
  • Cap the batch. “Stop after 50 and report credits used” keeps a CRM sweep predictable.
  • Re-check on a schedule, not on a loop. Job changes are slow-moving. Re-running the same list weekly doubles your spend for almost no new signal.
  • Chain the follow-up. A mover needs a new work email — the old one is dead. Pair with find_work_email.

Output

{ "profile_url": "https://linkedin.com/in/janedoe", "job_change": true, "new_company": "Ramp", "new_title": "VP Sales" }

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. People who move quietly, or who update months later, will read as “no change”. Treat a negative result as “nothing detected”, not as proof they are still in the seat.


ToolUse it instead when
check_promotionsThey stayed at the company but moved up — 2 credits
newly_hired_executivesYou are watching a company, not a person — 0.5 credits per profile
linkedin_profile_enrichYou want the whole work history, not just the change — 1 credit
find_work_emailYou already know they moved and need the new address

Next steps


Keep learning

Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.