Headcount by Department

Give it a LinkedIn company page, get back the headcount — total, or for one department.

Tool: headcount_by_department
Cost: 2 credits
Category: LinkedIn Company / Page
Required input: linkedin_page_url
Returns: Headcount, total or by department

What it does

Returns total headcount for a company, or headcount filtered by department.
Omit department for the total. Pass it — e.g. "Engineering", "Sales" — to scope the count.
This is a point-in-time snapshot. It tells you how big a team is now.
For change over time, use head_count_growth_rate instead. Same 2-credit price, different question.

Snapshot answers “is the sales team big enough to sell to”. Growth rate answers “is the sales team being built right now”. Pick the one your play needs.

Parameters

Parameter	Type	Required	Notes
`linkedin_page_url`	string	Yes	LinkedIn company page URL
`department`	string	No	e.g. `"Engineering"`, `"Sales"`. Omit for the total

How to use it

Connect the MCP server

Follow the setup guide for your client. Browser sign-in, no API key.

Get the total


What is the total headcount for linkedin.com/company/stripe?

Scope it to a department


How many people are in Sales at linkedin.com/company/stripe?

Qualify a list


For these 25 LinkedIn company pages, get the Engineering headcount. Drop any
company with fewer than 20 engineers.

Example prompts

Ask your client	What you get back
”Total headcount for linkedin.com/company/stripe”	One number, right now
”How big is their Sales team?”	Department-scoped count
”Which of these 25 accounts has 20+ engineers?”	One call per page, filtered by you
”Is that team growing?”	Different question — `head_count_growth_rate` at 2 credits

Best prompting practices

Say “right now” or “currently” when you want the snapshot. Words like “growing”, “trend” or “over time” should send your client to head_count_growth_rate.
Name the department explicitly. “Sales”, not “the revenue org”. Leave department off entirely when you want company total.
Pass a LinkedIn company page URL. This tool takes linkedin_page_url — a domain will not work here.
One department per call. Asking for three departments is three calls and 6 credits. Decide which one actually qualifies the account.
Cap the batch. “Stop after 25 and report credits used.”

Output


{
  "linkedin_page_url": "https://linkedin.com/company/stripe",
  "department": "Sales",
  "headcount": 1420
}

Credits and limits

2 credits per call, flat. Run check_credits (free) before a large batch.

Snapshot versus trend, same price: headcount_by_department gives you the count today, head_count_growth_rate gives you how that count has moved. Running both on one account is 4 credits — worth it on a shortlist, wasteful on a raw list.

Tool	Use it instead when
`head_count_growth_rate`	You need change over time, not a snapshot — 2 credits
`premium_linkedin_page_insights`	You want employee distribution plus growth and hiring in one call — 3 credits
`enrich_linkedin_page`	A rough employee count is enough — 0.5 credits
`find_people_within_company`	You want the actual people in that department, not the count — 0.3 credits

Next steps

All MCP tools — the full catalogue with credit costs
Signals & ABM — workflows that chain headcount into account scoring

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.