Find Mobile Number
/find-mobile-numberGive it a LinkedIn profile URL and get back that person's personal mobile number — 12 credits per lookup, so cap every batch.
Overview
`find_mobile_number` is a SyncGTM MCP tool that resolves a LinkedIn profile URL to that person's personal mobile number. At 12 credits a lookup it is one of the two most expensive tools on the server, tied with `find_work_phone`, and an empty result costs the same as a hit. Run it on people you have already decided to call, never on a raw export.
What it does
- 1
Takes one required input, `linkedin_url` — the full LinkedIn profile URL of the person you want to reach.
- 2
Accepts `first_name`, `last_name` and `organization_name` as optional extras. They cost nothing, raise the hit rate on sparse profiles, and stop a common name matching the wrong person.
- 3
Returns three fields: `mobile`, a `status`, and the `linkedin_url` you sent back for row matching. The number comes back with its country code (`+14155552671` in the docs example), which is the format `validate_whatsapp` expects.
- 4
Returns the personal line only. For the office or company number use `find_work_phone` at 12 credits, and for a published switchboard number `scrape_phones_from_website` at 0.5 credits.
- 5
An empty result means the number could not be found, not that the person has no mobile. Empties bill the full 12 credits.
- 6
12 credits per lookup, one person per call. There is no batch and no limit parameter, so 10 people costs 120 credits and 50 costs 600.
How to use it
- 1
Download the skill file — it saves as find-mobile-number.zip.
- 2
In Claude, open Settings → Capabilities → Skills and upload the .zip (or unzip the find-mobile-number/ folder into .claude/skills/ for Claude Code).
- 3
Connect the SyncGTM MCP server — browser sign-in, no API key — then run `check_credits` to see your balance. At 12 credits a lookup, a 25-row list is 300 credits.
- 4
Trigger `/find-mobile-number` and paste the LinkedIn profile URLs you want called. Include first name, last name and company in the same message wherever you have them: those three parameters are free and lift the hit rate.
- 5
Set the batch cap in the prompt — "stop after 10, do not retry empties, report credits used". The tool has no limit parameter of its own, so that one line is the setting most worth tuning.
Use cases
Top-of-pipeline cold calls
Pull mobiles for the handful of accounts carrying your largest open opportunities. The AE dials on Monday instead of waiting three days for an email reply.
Job-change re-engagement
A champion who bought from you before has moved to a new company. Get their mobile and call in week one, while the new stack is still being chosen.
Demo no-show recovery
Someone booked a demo and did not turn up. One call to a mobile reschedules the meeting where four follow-up emails do not.
Conference and event outreach
Get mobiles for the people you plan to meet onsite, then text them the morning of day one to lock in a coffee slot.
GTM workflow examples
Call the champions who just changed jobs
- 1Run `check_job_change` (2 credits, takes `profile_url`) on the 40 closed-won LinkedIn URLs in your CRM — 80 credits — and keep only the rows where `job_change` is true. Each mover comes back with `new_company` and `new_title`.
- 2Say 15 movers come back. Run `enrich_person` (1 credit) on those 15 — 15 credits — to confirm first name, last name and current organization, the three free parameters `find_mobile_number` wants.
- 3Cut the 15 to the 10 now sitting at ICP-fit companies with buying authority, and drop the rest before you spend a mobile credit.
- 4Run `check_credits` (free) to confirm 120 credits are available, then run `find_mobile_number` (12 credits) on those 10 LinkedIn URLs, passing `first_name`, `last_name` and `organization_name` on each call.
- 5Run `validate_whatsapp` (1 credit) on every `mobile` returned — up to 10 credits — so each row is tagged call-first or WhatsApp-first.
Outcome: A 10-row call sheet with mobile, WhatsApp flag, and the new title and new company that `check_job_change` returned — roughly 225 credits spent.
Recover last month's demo no-shows
- 1List the 12 people who booked a demo and did not attend, with the LinkedIn URLs held in your CRM.
- 2Run `check_job_change` (2 credits) on all 12 — 24 credits — and drop the 3 flagged as movers, leaving 9 still in the seat.
- 3Run `check_credits` (free), quote the 108-credit cost of the 9 lookups, and get sign-off before spending.
- 4Run `find_mobile_number` (12 credits) on the 9 remaining URLs, capped at 9, passing first name, last name and company on each call, with no retries on empties.
Outcome: A 9-row recovery sheet with mobile, status and the missed-demo date per person for about 132 credits, so the SDR can dial straight through it in one 30-minute block.
Build a mobile list from a viral industry post
- 1Run `linkedin_post_engagers` (0.3 credits per call) on the conference keynote post with `page_number` 1, then pages 2 and 3 — three calls, 0.9 credits — to collect the people who reacted.
- 2Run `enrich_person` (1 credit) on the 20 most senior reactors — 20 credits — for job title and company; the tool returns people, not contact details.
- 3Filter to the 8 who match your ICP and are attending in person, and discard the rest before any mobile lookup.
- 4Run `check_credits` (free), then `find_mobile_number` (12 credits) on those 8 profile URLs — 96 credits — passing `organization_name` on each call to disambiguate.
Outcome: An 8-name onsite outreach list with mobiles, ready to text on day one of the event — about 117 credits for the whole build.
Prompts
Paste any of these into Claude once the skill is installed and the SyncGTM MCP is connected.
Find the mobile number for linkedin.com/in/janedoe. Her name is Jane Doe and she works at Acme Corp — pass first_name, last_name and organization_name with the lookup.Check my SyncGTM credits first, then find mobile numbers for the 5 LinkedIn URLs pasted below. Stop at 5, do not retry empties, and report credits used.Find the mobile for linkedin.com/in/janedoe, then run validate_whatsapp on the number that comes back and tell me whether to call or message.Here are 30 LinkedIn URLs. Only the 8 marked Tier 1 get find_mobile_number — cap the run at 8, skip the rest, and show me the total cost before you start.Run check_job_change on these 12 CRM profile URLs, then find mobile numbers only for the ones it flags as movers. Cap the mobile lookups at 6 and report credits used.Best practices
Say "mobile" explicitly in the prompt. Ask for a "phone number" and your client may reach for `find_work_phone` and hand you a switchboard, for the same 12 credits.
Run `check_credits` (free) before every batch. A 50-row list is 600 credits, and an empty result bills exactly the same as a hit.
Cap the batch in the prompt: "stop after 10 and report credits used". At this price a cap is not optional, and the tool has no limit parameter of its own.
Always pass `first_name`, `last_name` and `organization_name` alongside `linkedin_url`. They add no cost and they are what stops a common name resolving to the wrong person.
Forbid retries. Add "do not retry empties" or a client will spend a second 12 credits querying the same providers for the same blank answer.
Qualify before you spend. If email will do, `find_work_email` is 1 credit; if a published main line is enough, `scrape_phones_from_website` is 0.5 credits.