Scrape Phones From Website
Give it a company website, get back every phone number published on it.
- Tool
scrape_phones_from_website- Cost
- 0.5 credits
- Category
- Website Scraping
- Required input
url- Returns
- Published phone numbers found on the site
What it does
- Crawls a company website and extracts every published phone number — page text,
tel:links, and embedded markup. - Covers the homepage plus contact, about, team, support and location pages.
- Returns switchboard, sales and office numbers rather than personal mobiles. You reach a front desk, not a decision-maker’s handset.
- Takes a website URL or a bare domain.
If you need the number of a specific person, this is the wrong tool. find_work_phone returns their office line and find_mobile_number returns their personal mobile — both 12 credits, both from a LinkedIn URL.
Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
url | string | Yes | Website URL or bare domain |
How to use it
Connect the MCP server
Follow the setup guide for your client. Browser sign-in, no API key.
Scrape one site
Scrape phone numbers from acme.com.Run it across a list
Scrape phone numbers from each of these 40 domains. Return one row per domain
with every number found and label each as switchboard, sales, or unknown.Pair it with a local-business build
For each Google Maps listing with a website, scrape phone numbers from that
site and compare them to the number on the listing.Escalate when you need a person
For the 10 accounts I flagged, find the mobile number for the named contact
from their LinkedIn URL instead.Example prompts
| Ask your client | What you get back |
|---|---|
| ”Scrape phone numbers from acme.com” | Every published number on the site |
| ”Get office numbers for these 40 domains” | One row per domain |
| ”Phone numbers for the businesses in this Maps list” | Chains from google_maps_listings |
| ”Get Jane Doe’s mobile” | Not this tool — use find_mobile_number |
Best prompting practices
- Set the expectation up front. Tell your client these are company lines, so it labels them as switchboard rather than dropping them into a mobile column.
- Pass the bare domain. You do not need a specific page — the crawl covers contact and location pages already.
- Forbid guessing. Numbers must come from the page. A plausible-looking fabricated number wastes a dial and burns the account.
- Escalate deliberately.
find_work_phoneandfind_mobile_numbercost 12 credits each. Reserve them for accounts you have already qualified. - Validate mobiles separately. If a scraped number does turn out to be a mobile,
validate_whatsapptells you whether it is reachable there.
Output
{
"url": "https://acme.com",
"phones": ["+1 512-555-0142", "+1 800-555-0110"]
}Credits and limits
0.5 credits per call. Run check_credits (free) before a large batch.
Plenty of sites publish no number at all. An empty result is normal, not an
error. Try
scrape_emails_from_website
for a contact inbox, or move to
find_work_phone if the account is worth
12 credits.
Related tools
| Tool | Use it instead when |
|---|---|
find_work_phone | You need one person’s office line — 12 credits |
find_mobile_number | You need one person’s personal mobile — 12 credits |
scrape_emails_from_website | You need published email addresses instead — 0.5 credits |
validate_whatsapp | You have a mobile and want to know if it is on WhatsApp — 1 credit |
Next steps
- All MCP tools — the full catalogue with credit costs
- Research & Web Scraping — 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.
SyncGTM MCP Mini CourseBeginnerMCP server · 8 lessons · 1h 31mAll 50 MCP tools clustered by GTM job — lead sourcing, CRM enrichment, social signals, account research, scraping — with copy-paste workflow prompts.AI-Powered GTMIntermediateApp + MCP · 19 lessons · 3h 6mWhere AI earns its cost, how to think in MCP tool chains, and three agentic builds — warm outbound, meeting research, CRM repair.