Skip to main content
Glama
mambalabsdev

mcp-gtm-hiring-signal-scraper

by mambalabsdev

GTM Hiring Signal Scraper MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

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, no https:// and no trailing slash. Example: stripe.com

  • role_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.com uses claylabs on 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

GTM Hiring Signal Scraper

D7O1SA2EqwHGsGr1P

GTM Tech Stack Signal Enrichment

qyd7nNyqFPelQViBx

GTM Signals Aggregator

xKdRfnfFNkdMpFuNs

Job Board Keyword Signal Scanner

4DvqpvhMR74NLcDDY

Domain to LinkedIn URL Resolver

3HtnSaqPHOg1Qg5gx

ICP Fit Scorer

W161DT8W4kW55dMFh

Domain Deliverability Checker

0tVgxI7A6o9jMlxmc

Company Firmographic Enricher

YlUtLWjfPpqykmB8g

Company Social Presence Mapper

4k6CCemkgBDz18m2h

Company Identity Resolver

lr8fTRAmZCBZmuwwh

Company Change-Event Feed

oX44rS0fkEJ3rXLWe

Funding & Press Signal Scanner

FS13X6dhQVgX3XOM6

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Available Tools

1 tool
scan_gtm_hiring_signalsScan GTM Hiring SignalsA
Read-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.

ParametersJSON Schema
NameRequiredDescriptionDefault
domainYesBare company domain without https:// and without a trailing slash. Example: stripe.com
role_filterNoOptional list of GTM role keywords to filter on. Defaults to the built-in GTM keyword list if omitted.
ats_slugNoOptional 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

A4.3/5.0
Behavior4/5

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.

Conciseness5/5

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.

Completeness5/5

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.

Parameters3/5

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.

Purpose5/5

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.

Usage Guidelines4/5

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. 1 tool updatev1.0.4
    • First observedscan_gtm_hiring_signals

TDQS

A4.2/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is unique and clearly defined.

Naming Consistency5/5

The single tool name 'scan_gtm_hiring_signals' follows a clear verb_noun pattern and is descriptive, making it consistent within the server.

Tool Count3/5

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.

Completeness3/5

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

ActivityMaintained
ResponsivenessResponsive

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

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Scans job boards for keyword patterns that indicate buying intent, technology adoption, or team expansion. Returns structured signal data for outbound targeting.
    1
    186
    2
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    GTM 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.
    11
    162
    1
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables 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.
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    Transforms job postings into qualified sales leads by searching for active jobs, enriching company data, and identifying decision-maker contact information.
    -

Latest Blog Posts

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