Skip to main content
Glama
mcp-gtm-hiring-signal-scraper

mcp-gtm-hiring-signal-scraper

Scan GTM Hiring Signals

scan_gtm_hiring_signals
Read-onlyIdempotent

Scans company career pages and job boards to detect GTM hiring activity. Returns role counts and signal strength to qualify accounts before outreach or track hiring velocity.

Instructions

Scan company career pages to detect GTM hiring activity: open sales, marketing, and revenue operations roles, a role count, and a high, medium, or low signal strength. Reads the Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Personio job boards; a company on any other board returns a null ats_platform and a zero count, not an error. Use it to qualify an account before outreach, or on a schedule in velocity mode to see whether a company is ramping its GTM team. Use mode batch with domains for a list in one call. Output is Clay-ready flat JSON, one row per company. Requires an APIFY_TOKEN and consumes Apify credits per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "scan_gtm_hiring_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoProcessing mode. "single" scores the domain. "batch" scores every entry in domains in one run, one row per company. "velocity" compares this run against previous_gtm_role_count and previous_run_date to report role changes since last time. Default: "single".
domainYesBare company domain without https:// and without a trailing slash. Example: stripe.com
domainsNoList of bare domains to scan in one run when mode is "batch", for example ["stripe.com", "figma.com"]. One row per company. The run timeout is 1,800 seconds; a very large batch can still reach it.
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.
role_filterNoOptional list of GTM role keywords to filter on. Defaults to the built-in GTM keyword list if omitted.
previous_run_dateNoISO date of the previous run for this domain, e.g. 2026-07-15. Used in velocity mode to report days between runs.
include_role_detailsNoWhen true, include the full per-role detail array (title, department, location, url) in the output. Default: false.
previous_gtm_role_countNoGTM role count from the previous run for this domain. Used in velocity mode to compute the delta, which is what makes a scheduled run cheap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.0.7
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domains
      Added value: +{
      +  "description": "List of bare domains to scan in one run when mode is \"batch\", for example [\"stripe.com\", \"figma.com\"]. One row per company. The run timeout is 1,800 seconds; a very large batch can still reach it.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / include_role_details
      Added value: +{
      +  "description": "When true, include the full per-role detail array (title, department, location, url) in the output. Default: false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "Processing mode. \"single\" scores the domain. \"batch\" scores every entry in domains in one run, one row per company. \"velocity\" compares this run against previous_gtm_role_count and previous_run_date to report role changes since last time. Default: \"single\".",
      +  "enum": [
      +    "single",
      +    "batch",
      +    "velocity"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / previous_gtm_role_count
      Added value: +{
      +  "description": "GTM role count from the previous run for this domain. Used in velocity mode to compute the delta, which is what makes a scheduled run cheap.",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / previous_run_date
      Added value: +{
      +  "description": "ISO date of the previous run for this domain, e.g. 2026-07-15. Used in velocity mode to report days between runs.",
      +  "type": "string"
      +}
  2. First observedv1.0.4

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly/idempotent/openWorld/non-destructive, but the description adds materially: unsupported boards return a null ats_platform and zero count rather than an error, an APIFY_TOKEN is required, Apify credits are consumed per call, and output is flat one-row-per-company JSON. These are exactly the operational facts annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, followed by capability limits, usage, and operational constraints in a logical order. The six-board enumeration and the dual mention of velocity mode add slight length but each sentence carries load.

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?

With no output schema, the description compensates by describing the return shape (Clay-ready flat JSON, one row per company, optional per-role detail). Auth requirements, cost, board coverage, and error semantics are all covered, leaving nothing an agent needs to call this correctly.

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 the schema already documents all eight parameters including mode enums and defaults. The description only restates the batch+domains pairing and velocity mode framing, adding no syntax or format detail beyond the schema; baseline 3 is appropriate.

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?

States a specific verb (scan) and resource (company career pages), names the exact signal it extracts (GTM hiring activity, role count, signal strength), and even enumerates the supported ATS boards. There are no siblings to distinguish from, but the scope is unambiguous without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete use cases ('qualify an account before outreach' and 'on a schedule in velocity mode') and routes batch work explicitly ('Use mode batch with domains for a list in one call'). No alternatives exist to exclude, so this is as complete as the context allows.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools