mcp-gtm-hiring-signal-scraper
This server scans company career pages to detect go-to-market (GTM) hiring activity, returning structured, Clay-ready JSON data on sales, marketing, and revenue operations roles.
Detect GTM hiring signals by providing a bare company domain (e.g.,
stripe.com)Auto-detect ATS platform using cascading logic across Greenhouse, Lever, and Ashby, with optional
ats_slugoverride for edge cases (e.g.,claylabsforclay.com)Filter roles by custom keywords via optional
role_filter, or use the built-in GTM keyword listReceive structured flat JSON output including:
Detected ATS platform
Count of open GTM roles
Matched role titles, categories, and seniority
Signal strength rating (high, medium, or low)
Top GTM role and career page URL
Feed results directly into Clay, a CRM, or AI agent workflows thanks to the flat JSON format designed for column mapping
Handle unsupported ATS platforms gracefully — companies not on Greenhouse, Lever, or Ashby return a null platform and zero role count without errors
Scans Greenhouse job boards for go-to-market roles, returning structured data on hiring signals.
GTM Hiring Signal Scraper MCP Server
An MCP server that detects go-to-market hiring activity from company career pages. It wraps the Mamba Labs GTM Hiring Signal Scraper on Apify and returns Clay-ready flat JSON to any MCP client.
What's Inside
Related MCP server: mcp-gtm-suite
What it does
Give it a company domain and it scans that company's job board for sales, marketing, and revenue operations roles across Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Personio. You get back a structured read on how hard that company is hiring for go-to-market, ready to drop into Clay, a CRM, or an AI agent workflow. All of the scraping runs on Apify. This package is a thin client that calls the actor and hands back the result.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config:
{
"mcpServers": {
"mamba-gtm-hiring": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-gtm-hiring-signal-scraper"],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The scan_gtm_hiring_signals tool will be available.
Prerequisites
Node.js 18 or newer
An Apify account with an API token
Example prompts
"Check if stripe.com is hiring for go-to-market roles right now."
"Scan openai.com for sales and revenue operations job postings."
"Is datadoghq.com ramping up GTM hiring? Use the GTM hiring scanner."
"Pull the GTM hiring signal for figma.com and list which roles are open."
Inputs
domain(required): the bare company domain, nohttps://and no trailing slash. Example:stripe.comrole_filter(optional): a list of GTM role keywords to filter on. Leave it out to use the built-in keyword list.ats_slug(optional): override the ATS board slug when it differs from the domain. Example:clay.comusesclaylabson Ashby.
Output
The tool returns the actor's flat JSON for the scanned company. Fields include the detected ATS platform, the count of open GTM roles, the matched role titles and their categories, and a seniority read. Companies on an ATS outside those six come back with a null platform, a zero role count, and no error. See the Apify Store page for the full output schema.
Example output
{
"domain": "stripe.com",
"company_name": "Stripe",
"gtm_hiring_signal": true,
"ats_platform": "greenhouse",
"gtm_role_count": 12,
"signal_strength": "high",
"top_gtm_role": "Head of Revenue",
"career_page_url": "https://boards.greenhouse.io/stripe",
"run_date": "2026-05-28"
}Features
Cascading ATS detection: Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Personio
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
Full actor documentation
This server is a thin client and holds no scraping logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:
https://apify.com/mambalabs/gtm-hiring-signal-scraper
Mamba Labs GTM Suite
This server is part of the Mamba Labs GTM Suite, a fleet of twelve specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor.
Actor | Immutable Actor ID |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
Built by Mamba Labs | npm | Apify Store
License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
Available Tools
1 toolscan_gtm_hiring_signalsScan GTM Hiring SignalsARead-onlyIdempotent
Scan company career pages to detect GTM hiring activity. Returns structured data on sales, marketing, and revenue operations job postings. Supports Greenhouse, Lever, and Ashby ATS platforms. Output is Clay-ready flat JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Bare company domain without https:// and without a trailing slash. Example: stripe.com | |
| role_filter | No | Optional list of GTM role keywords to filter on. Defaults to the built-in GTM keyword list if omitted. | |
| ats_slug | No | Optional ATS board slug override for when it differs from the domain. Example: clay.com uses claylabs on Ashby. If omitted, the scraper auto-probes common slug variants. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), the description adds valuable behavioral details: requires APIFY_TOKEN, consumes Apify credits, and supports specific ATS platforms. No contradictions with annotations. The description enriches transparency by specifying auth and cost implications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise (4 sentences), front-loaded with the main action, and includes only essential information (purpose, output, platforms, requirements). Every sentence adds value with no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema, the description compensates by specifying the output format (Clay-ready flat JSON). It also covers supported platforms, auth requirements, and credit consumption. For a scanning tool with 3 parameters and clear annotations, the description provides all necessary context for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description does not add significant new meaning beyond the parameter descriptions, though it reinforces the ATS platform support. No additional parameter semantics or examples are provided that aren't already in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool scans company career pages for GTM hiring activity, specifying the types of jobs (sales, marketing, revenue operations) and supported ATS platforms (Greenhouse, Lever, Ashby). Output format is explicitly described as Clay-ready flat JSON. With no sibling tools, differentiation is unnecessary, and the purpose is fully conveyed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description provides explicit context on when to use (detecting GTM hiring signals) and operational requirements (requires APIFY_TOKEN, consumes credits). While no alternative tools are listed (siblings are absent), the description clearly implies the use case and prerequisites, making the guidance adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.4- First observed
scan_gtm_hiring_signals
TDQS
With only one tool, there is no possibility of confusion between tools. The tool's purpose is unique and clearly defined.
The single tool name 'scan_gtm_hiring_signals' follows a clear verb_noun pattern and is descriptive, making it consistent within the server.
The server has only one tool, which is on the low end. While the tool is non-trivial and serves a specific function, the scope of the server might benefit from additional tools (e.g., for configuration or filtering) to be more comprehensive.
The single tool covers the core task of scanning for GTM hiring signals, but lacks auxiliary features like specifying target companies or managing multiple scans, which could be considered notable gaps.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Find companies hiring for a role and geo, qualify them, and watch them for changes.
Search job postings, companies, and technology stacks across 10M+ companies.
Real-time B2B buying signals on your target accounts: funding, hiring, leadership, tech stack.
B2B sales intelligence — company emails, enrichment, lead lists, hiring & funding signals.
Related MCP Servers
- AlicenseAqualityCmaintenanceScans job boards for keyword patterns that indicate buying intent, technology adoption, or team expansion. Returns structured signal data for outbound targeting.11862MIT
- AlicenseAqualityAmaintenanceGTM signal intelligence suite for AI agents. Six tools: hiring signals, tech stack detection, company-to-LinkedIn resolution, ICP scoring, job board scanning, and a combined signals aggregator. Built for outbound sales workflows.111621MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to pull live job listings from major ATS platforms (Greenhouse, Lever, Ashby, Workable), Hacker News hiring threads, and detect hiring signals on company career pages.-
- FlicenseNot gradedqualityDmaintenanceTransforms job postings into qualified sales leads by searching for active jobs, enriching company data, and identifying decision-maker contact information.-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambalabsdev/mcp-gtm-hiring-signal-scraper'
If you have feedback or need assistance with the MCP directory API, please join our Discord server