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. 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. |
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 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.