ATS MCP Server
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_boardA | Find which job boards carry a company's postings. Checks each source and reports every one that has the company, so a company on both Greenhouse and LinkedIn shows up as both. Results are remembered for the process lifetime. |
| register_boardA | Pin a board explicitly when discovery can't guess it. Read the coordinates off the careers URL:
|
| search_jobsA | Search one company's open roles across job boards. Public boards are searched concurrently. A source that has nothing for
this company contributes nothing; a source that fails is reported in
|
| search_manyA | Search several companies and return one merged list. Companies run in sequence so a throttled source paces properly rather
than firing every request at once. A company found on no board is listed
in |
| get_jobA | Full detail for one posting, including its description. |
| classify_titleA | Judge one job title without touching the network. Exposes the same heuristics the search filters use, so a caller can see how a title will be treated before trusting a filtered search. |
| source_statusA | Which sources are configured, and what quota is left. Public boards report as always available. LinkedIn reports whether the delegated server is reachable, plus its throttle state, so a caller can tell "not configured" apart from "quota spent". |
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 7 tools
Each tool has a clearly distinct role: discovery (find_board), manual pinning (register_board), single-company search (search_jobs), multi-company search (search_many), detail retrieval (get_job), local classification (classify_title), and source diagnostics (source_status). There is minimal overlap, and the descriptions clarify boundaries like one vs. many companies.
Almost all tools use a consistent snake_case verb_noun pattern: find_board, register_board, search_jobs, search_many, get_job, classify_title. source_status breaks the pattern by starting with a noun, a minor inconsistency. Overall readable and predictable.
Seven tools is well-scoped for an ATS/job-board search server; each tool covers a distinct operation without redundancy. The count supports core discovery, search, detail, classification, and status workflows.
The surface covers discovery, source registration, single/multi-company search, job detail, title classification, and source status, which are the main lifecycle operations for this domain. Minor gaps exist, such as no explicit board-removal or broader source-listing operation, but agents can work around these.