JobLens MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADZUNA_APP_ID | Yes | Your Adzuna API App ID | |
| ADZUNA_APP_KEY | Yes | Your Adzuna API App Key |
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_jobsB | Search live job postings. Args: query: role or keywords, e.g. "machine learning engineer" location: city/region filter, e.g. "Atlanta, GA" (optional) country: 2-letter country code Adzuna supports (default "us") results_per_page: how many postings to return (max ~50) |
| list_job_categoriesA | List the job categories the search API supports for a given country. |
| parse_resumeA | Parse a local resume file (PDF or .txt) into structured data: extracted skills, email, and phone number. The file never leaves your machine — this just reads it locally. Args: file_path: absolute path to the resume file on disk |
| match_resume_to_jobA | Score how well a parsed resume matches a job description, based on skill-keyword overlap. Returns a 0-100 score plus matched/missing skills. Args: file_path: absolute path to the resume file (parsed automatically if not cached) job_description: the job posting text to match against |
| search_and_matchA | Convenience tool: search live jobs, then rank each result by how well it matches the given resume. Returns jobs sorted by match score (desc). Args: file_path: absolute path to the resume file query: role or keywords to search for location: city/region filter (optional) country: 2-letter country code (default "us") results_per_page: how many postings to fetch before ranking |
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 5 tools
Each tool has a distinct purpose: listing categories, parsing resumes, matching a resume to a job, searching jobs, and a convenience combiner. The descriptions clearly differentiate them, even the combined search_and_match is clearly a hybrid of search_jobs and match_resume_to_job.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., list_job_categories, parse_resume, search_jobs. The naming is predictable and easy to interpret.
With 5 tools, the server is well-scoped for its purpose: listing categories, parsing, matching, searching, and a combined tool. Each tool earns its place without redundancy or bloat.
The tool set covers the core workflow of parsing, matching, and searching jobs. A minor gap is the lack of a tool to list supported countries or retrieve job details by ID, but the existing tools handle primary use cases effectively.