mcp-adzuna
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADZUNA_APP_ID | Yes | Your Adzuna app ID from https://developer.adzuna.com/signup | |
| ADZUNA_APP_KEY | Yes | Your Adzuna app key from https://developer.adzuna.com/signup |
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 Adzuna's job listings. country: ISO country code Adzuna covers, e.g. "gb", "us", "de", "fr", "it".
what: keywords where ALL words must match (AND). For multi-word roles like
"Senior Lead Data Engineer" this can silently return zero results;
use what_or instead to match ANY of the words.
what_or: keywords where ANY word may match (OR) - higher recall than |
| list_categoriesA | List Adzuna's job category tags for a country (e.g. "it-jobs", "sales-jobs"). country: ISO country code, e.g. "gb", "us", "de".
Category tags returned here can be passed as the |
| salary_histogramA | Get the current distribution of salaries for a job search as a histogram. Each key in the returned histogram is the lower bound of a salary band; the value is the number of vacancies whose salary falls in that band. country: ISO country code, e.g. "gb", "us", "de". what: keywords to filter jobs by (AND semantics, all words must match). category: a category tag as returned by list_categories. location: a hierarchical place, most general first, e.g. ["UK", "London"]. See regional_data for how to discover valid values. |
| top_companiesA | Get a leaderboard of the top 5 employers by number of vacancies. country: ISO country code, e.g. "gb", "us", "de". what: keywords to filter jobs by (AND semantics, all words must match). category: a category tag as returned by list_categories. location: a hierarchical place, most general first, e.g. ["UK", "London"]. See regional_data for how to discover valid values. |
| regional_dataA | Get vacancy counts for each sub-region of a given location. Also useful for discovering the exact country: ISO country code, e.g. "gb", "us", "de". category: a category tag as returned by list_categories. location: a hierarchical place, most general first, e.g. ["UK", "West Midlands"]. Omit to get the country's top-level regions. |
| historical_salaryA | Get average salary by month for a category and/or location, over time. Returned keys are "YYYY-MM" strings; order is not guaranteed by the API. country: ISO country code, e.g. "gb", "us", "de". category: a category tag as returned by list_categories. months: how many months of history to return. location: a hierarchical place, most general first, e.g. ["UK", "London"]. See regional_data for how to discover valid values. |
| api_versionA | Get the current Adzuna API version - useful for debugging connectivity/auth. |
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 targets a distinct aspect: job search, category listing, salary distribution, top companies, regional breakdown, historical salary, and API version. There is no overlap, and descriptions clearly differentiate each tool's purpose.
Tool names follow a mix of verb_noun (search_jobs, list_categories) and noun_phrase (salary_histogram, top_companies, regional_data, historical_salary, api_version) patterns. All are lowercase with underscores, but the lack of a consistent verb prefix makes the naming pattern inconsistent.
With 7 tools, the server is well-scoped for a job search and analytics domain. Each tool serves a distinct purpose without redundancy or bloat.
The server covers the core job search workflow, including filtering, category discovery, salary analysis, and regional breakdowns. However, there is no explicit tool for fetching a single job's full details or for paginating beyond setting a page size, leaving minor gaps in the lifecycle.