ats-jobs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsA | Fetch live job postings for named companies straight from their ATS board API. Companies are 'provider:slug' pairs (lever:palantir) or career-site URLs; use resolve_company first if you only have a name. Filters are applied before billing, so a narrow query is cheap. Billed to your own Apify account at $0.002 per returned job row: max_jobs is the hard spend cap. |
| list_supported_atsA | List the applicant-tracking systems this server can read, and the 'provider:slug' form search_jobs expects for each. No network, no cost. |
| resolve_companyA | Map a company name or career-site URL to the 'provider:slug' pair that search_jobs takes, using the public CC-BY ats-directory. A URL is read directly; a name is matched against the directory. Returns every match, with 'status' saying whether that board answered when last probed (ok / dead / unconfirmed). Free — no Apify run, no billing. |
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 3 tools
Each tool has a distinct responsibility: searching live jobs, listing supported ATS integrations, and resolving company names/URLs to provider-slug pairs. There is no overlap or ambiguity between them.
All three tools use a consistent snake_case verb-first pattern: search_jobs, list_supported_ats, resolve_company. The naming clearly signals action and object.
Three tools is an appropriate size for this server's focused purpose. Each tool is necessary and contributes a distinct step in the workflow from company name to actual job postings.
The tool set covers the full intended workflow: discover supported ATS platforms, resolve a company to the expected identifier, then search live job postings. No obvious missing operations or dead ends are apparent for the stated purpose.