JobsDirect MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOBSDIRECT_OUTPUT_DIR | No | Directory where output files (Word exports, the tracker CSV) are written. Defaults to your Desktop, else ~/JobsDirect. |
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": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsC | Search open job postings. |
| get_job_detailsA | Full description, criteria and open/closed status for a job ID (LinkedIn) or any posting URL. |
| evaluate_job_fitB | Score candidate-to-job fit 0-100 with the 4-tier ATS engine. Tiers: industry/domain affinity (40), degree + years gate (20), skills overlap (30), language and work-authorisation gate (10, a missing required language fails the gate). |
| generate_cover_letterC | Draft a short cover letter that cites the candidate's two most relevant achievements. |
| export_to_docxB | Save Markdown text (resume, cover letter, report) as a Word .docx in the output folder. |
| prepare_job_applicationB | One call: fetch the posting, score fit, tailor the resume and draft the cover letter. |
| track_applicationC | Manage the applications CSV (job_applications.csv in the output folder). |
| lookup_salary_benchmarkB | Indicative junior/mid/senior annual salary bands for a role in US, EU, UK, Türkiye or remote. |
| tailor_resumeB | Re-rank the candidate's own CV bullets by relevance to the job, list matched/missing keywords, and flag bullets that need a metric. Returns Markdown (feed it to export_to_docx). |
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 9 tools
Most tools have distinct purposes, but prepare_job_application overlaps heavily with get_job_details, evaluate_job_fit, tailor_resume, and generate_cover_letter by bundling them into one workflow shortcut. Agents may be unsure whether to call the composite tool or the granular tools for a given request, though the descriptions make the tradeoff reasonably clear.
All tool names use snake_case and follow a predictable verb_noun or verb_noun_phrase pattern, such as search_jobs, get_job_details, evaluate_job_fit, and generate_cover_letter. export_to_docx is a minor phrasing variation but still fits the consistent imperative naming style.
Nine tools are well-scoped for a job-search and application-preparation server, with each major workflow step represented. The count is neither thin nor sprawling, and the composite tool does not inflate the surface excessively.
The surface covers the core lifecycle: search jobs, inspect details, evaluate fit, tailor resume, generate cover letter, export documents, track applications, and benchmark salary. Minor gaps remain around richer application tracking operations and explicit candidate-profile management, but agents can work around them.