GTM Hiring Signal Scraper

What is GTM Hiring Signal Scraper?

A thin MCP server that scans company career pages for go-to-market (GTM) hiring signals. It wraps the Mamba Labs GTM Hiring Signal Scraper on Apify and returns Clay-ready flat JSON to any MCP client. Designed for sales teams, revenue operations, and AI agent workflows that need a read on how hard a company is hiring for sales, marketing, and revenue operations roles.

How to use GTM Hiring Signal Scraper?

Configure it in an MCP client (e.g., Claude Desktop) by adding the server JSON with "command": "npx", "args": ["-y", "@mambalabsdev/mcp-gtm-hiring-signal-scraper"] and the APIFY_TOKEN environment variable. After restarting the client, use the scan_gtm_hiring_signals tool with a company domain. Prerequisites: Node.js 18+ and an Apify account with an API token.

Key features of GTM Hiring Signal Scraper

• Cascading ATS detection: Greenhouse, Lever, Ashby
• GTM role filtering with 3-tier signal strength (high, medium, low)
• Flat JSON output designed for Clay column mapping
• Optional role_filter and ats_slug inputs

Use cases of GTM Hiring Signal Scraper

• Check if a target company is actively hiring for go-to-market roles
• Scan multiple domains for sales and revenue operations job postings
• Detect GTM hiring ramp-ups as an early signal for outreach timing
• Pull structured hiring data into a CRM, Clay table, or AI agent

FAQ from GTM Hiring Signal Scraper

What does the GTM Hiring Signal Scraper detect?

It detects go-to-market hiring activity by scanning a company’s job board for sales, marketing, and revenue operations roles. It returns a structured signal on how aggressively the company is hiring for those roles.

Which ATS platforms are supported?

Greenhouse, Lever, and Ashby are explicitly supported. Companies using other ATS platforms return a null platform, zero role count, and no error.

What inputs does the tool require?

The only required input is a bare company domain (e.g., stripe.com). Optional inputs include a role_filter list of GTM keywords and an ats_slug to override the ATS board slug when it differs from the domain.

Do I need an Apify account and token?

Yes. You must have an Apify account and set the APIFY_TOKEN environment variable. The token is obtained from the Apify console. All scraping runs on Apify.

What does the output look like?

The output is flat JSON with fields such as domain, company_name, gtm_hiring_signal (boolean), ats_platform, gtm_role_count, signal_strength, top_gtm_role, career_page_url, and run_date.