Headcount by Department

Give it a LinkedIn company page, get back the headcount — total, or for one 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.

Use cases

• Qualify on the team you sell to. A sales tool needs a sales team; total headcount does not tell you whether one exists.
• Set a minimum team size. Department counts turn “big enough to need this” into a rule you can apply across a list.
• Size the deal before the call. Seat-based pricing follows the department count, so the number decides which package you pitch.
• Separate lookalike accounts. Two 300-person companies split cleanly once you know one runs 60 in sales and the other six.

How to use it

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

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

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

Example prompts

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. If your list holds domains, resolve them once with enrich_organization rather than letting the client guess a page URL per row.
• One department per call. Asking for three departments is three calls and 6 credits. Decide which one actually qualifies the account.
• State the qualifying threshold. “Keep accounts with 10 or more in sales, drop the rest, tell me how many survived.” Without a number your client returns counts and you do the filtering by hand.
• Ask for the count as a number. “Return company, department, headcount” — “a sizeable sales team” is not something you can sort a list on.
• Qualify on the team, not the company. A 300-person account with six people in sales is not a sales-tooling buyer, and total headcount will never tell you that.
• 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.

Parameters

Related tools

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.