mcp-job-board-keyword-signal-scanner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token |
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_job_board_keywordsA | Scan a company's job board for roles in chosen categories across Greenhouse, Lever, Ashby, Workday, and Rippling. Pick from GTM, Engineering, Finance, Operations, Executive, or supply custom keywords. Returns a flat, Clay-ready JSON row of matched role counts and titles per category. 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
There is only one tool, so there is no possibility of misselection or overlapping purpose. Its scope (scanning a company's job board for keyword matches across several ATS platforms) is stated clearly and unambiguously.
The single name 'scan_job_board_keywords' follows a clear verb_noun pattern in snake_case, which is readable and idiomatic. With only one tool there is no pattern to verify across the set, so it cannot be judged fully consistent.
A single tool is thin for a server, even though this one is substantive and well-scoped rather than trivial. Common adjacent needs (multi-company scans, listing supported boards, output shaping) would naturally live here, making one tool feel minimal.
The core read-only scanning operation is covered, including category selection and custom keywords, but there are notable gaps: no batch/multi-company scanning, no way to discover supported boards or categories programmatically, and no output configuration. Agents can still accomplish the primary task, but only one company per call and with fixed output.