A count of open roles is a stock; velocity is a flow, and they tell you different things — a large static board and a small fast-moving one look identical on the headline number. Exposing both is what makes this usable for a decision about timing rather than only about applying. The counts attached to sectors and locations serve the same purpose at a smaller scale: they turn a taxonomy into a signal about where the activity is. Narrow by design — this is the recruiting job market and nothing else — which is what lets the taxonomy be specific enough to be useful.
A job-board client narrowed to one vertical — recruiter and talent-acquisition roles — with seven tools covering jobs, companies, sectors, locations and aggregate market statistics.
- search_jobs covers live listings; get_job returns one by slug with the complete detail rather than the search summary.
- list_companies browses the recruiting agencies with their active counts, and get_company returns a full profile plus a paginated list of that agency's open roles.
- list_sectors and list_locations return the taxonomies with active job counts attached, and the location tool covers the hierarchy — countries, regions or cities.
- market_stats returns the aggregate picture including posting velocity over 24 hours and 7 days, which is a different question from how many jobs are open.
RECRUITER_ROLES_API_KEY.
One command plus a key — RECRUITER_ROLES_API_KEY=rr_live_YOUR_KEY npx recruiter-roles-mcp, then supply credentials