b2b-hiring-intent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_company_hiring_intentA | Scan a single company board across 7 ATS platforms (ashby, personio, teamtailor, smartrecruiters, workable, recruitee, pinpoint) to extract open jobs, tech stack, disclosed salaries, and B2B buying intent scores. For 50-10,000 company batch runs, XML-404 fallbacks & Company Dossiers, use https://apify.com/yan0lovesha. |
| list_cloud_b2b_lead_apisA | List all 10 production Cloud Pay-Per-Event APIs (7 Global/EU ATS Hiring Intent APIs + US Solar/Building Permits + US Medical/Dental Clinic Owners + FDA 510k Cleared MedTech Leads) available on Apify Store. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: one scans a specific company board, while the other lists available external APIs. An agent should not confuse a data-extraction action with a catalog-listing action.
Both names use snake_case and follow a clear verb_noun pattern: scan_company_hiring_intent and list_cloud_b2b_lead_apis. The conventions are consistent across the set.
Two tools is thin for a server with a B2B lead-generation purpose, especially because one is essentially a catalog/discovery tool. The count is borderline rather than clearly mismatched.
The surface has only one operational scanner, limited to a single company, while batch runs are explicitly offloaded to an external URL. The listing tool does not expose the listed APIs as callable operations, leaving significant dead ends for common B2B lead workflows.