j-hunt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JHUNT_DB_PATH | No | Path to the SQLite database file (default: data/jhunt.db) | |
| GOOGLE_MAPS_API_KEY | No | Optional API key for Google Maps geocoding and map-region search |
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 | Search job listings across configured sources. Provide |
| search_jobs_in_regionA | Search jobs inside a map-selected rectangular region (a bounding box). Pass the north-east and south-west corners of the selected area. Requires GOOGLE_MAPS_API_KEY (job locations are geocoded to test containment). |
| geocode_locationB | Resolve a place name to coordinates + a formatted address (Google Maps). |
| save_jobC | Persist a job (e.g. one returned by search) so it can be tracked. |
| list_saved_jobsA | List all jobs that have been saved locally. |
| log_applicationA | Record an application for a job (by saved job_id or an ad-hoc url). Creates the application, or updates the existing one for that job. |
| update_application_statusB | Move an application to a new status (validates allowed transitions). |
| set_next_actionC | Set a follow-up reminder (date + note) on an application. |
| list_applicationsB | List tracked applications, optionally filtered by status. |
| get_profileA | Return the stored job-hunt profile (name, skills, resume, preferences). |
| update_profileC | Update profile fields. Only the fields you pass are changed. |
| set_resumeC | Store/replace the resume text used by the tailoring prompts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tailor_resume | Tailor the stored resume to a specific job description. |
| draft_cover_letter | Draft a cover letter for a saved job using the stored profile. |
| application_followup_email | Draft a polite follow-up email for a tracked application. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| profile_resource | The stored job-hunt profile as JSON. |
| resume_resource | The current resume text (empty if not set). |
| saved_jobs_resource | All locally saved jobs as JSON. |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: geocoding, profile management, job searching with two variants, saving jobs, logging applications, tracking status, setting follow-up actions, and updating resume. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_applications, save_job, update_application_status). The only minor variant, search_jobs_in_region, still adheres to the pattern with a qualifier.
12 tools cover the core workflows of a job hunt assistant: searching, saving, applying, tracking, profile/resume management, and geolocation. The count is well-scoped without redundancy.
The tool surface covers search, save, apply, status updates, follow-up actions, and profile management. Minor gaps exist (no delete operations for saved jobs or applications), but these are non-critical for the domain.