mcp-gtm-hiring-signal-scraper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token for authentication |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_gtm_hiring_signalsA | 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. |
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 1 tool
With only one tool, there is no possibility of tool misselection or overlapping purposes. The single tool has a clearly defined scope and internal modes that do not create cross-tool ambiguity.
The tool name 'scan_gtm_hiring_signals' follows a clear snake_case verb_noun pattern. With only one tool, consistency is inherently perfect.
A single tool is borderline thin for the server's purpose. While it covers the core scanning operation, the rubric treats 1-2 tools as marginal, and there is no separate tool for configuration, result retrieval, or board management.
The tool covers scanning across multiple ATS platforms, batch mode, velocity mode, and outputs structured JSON. For the narrow purpose of detecting GTM hiring signals, the surface is largely complete, with only minor potential gaps like separate board listing or historical trend queries.