JobMatch MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADZUNA_APP_ID | No | Your Adzuna application ID. Optional; if not set, search_jobs automatically uses a deterministic mock dataset. | |
| ADZUNA_APP_KEY | No | Your Adzuna application key. Optional; if not set, search_jobs automatically uses a deterministic mock dataset. | |
| JOBMATCH_DB_PATH | No | Absolute filesystem path to the SQLite database file used by the application tracker. Optional; if omitted, the server uses its default database location. |
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 |
|---|---|
| search_jobsA | Search live job postings by title/keyword and optional location. |
| score_resume_matchB | Score how well a resume matches a specific job description. |
| track_applicationA | Create a new tracked application, or update an existing one by id. |
| list_applicationsA | List tracked applications, optionally filtered by pipeline status. |
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 4 tools
Each tool targets a distinct function: searching jobs, scoring resume-job match, tracking/updating applications, and listing applications. There is no overlap or ambiguity between their purposes.
All tool names follow a consistent snake_case verb_noun pattern (search_jobs, score_resume_match, track_application, list_applications). The style is uniform and predictable.
With only 4 tools, the server is tightly scoped to its job-match niche. Each tool is essential and covers a distinct step in the user's workflow without redundancy.
The server covers the core workflow of searching jobs, matching resumes, and managing applications. Minor gaps exist (e.g., no delete application or detailed single-application view), but agents can safely navigate the current surface.