Skip to main content
Glama
fabioba

mcp-adzuna

by fabioba

search_jobs

Search Adzuna's job database with filters for location, keywords, salary, and employment type to find matching job openings.

Instructions

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 what. what_and: same as what (all words must match), explicit alternate name. what_phrase: an exact phrase that must appear in the title or description. what_exclude: keywords to exclude from results. title_only: keywords to match, restricted to the job title only. where: geographic centre of the search - a city, region, or postal code (NOT a country name; combine with country for that). A bad value here silently returns no results rather than erroring. distance: search radius in km around where. Defaults to 5km if omitted. location: a hierarchical place, most general first, e.g. ["UK", "South East England", "Buckinghamshire"]. See regional_data for how to discover valid values. category: a category tag as returned by list_categories. sort_by / sort_dir: how to order results (e.g. sort_by="salary"). salary_min / salary_max: salary bounds to filter on. salary_include_unknown: also include jobs with no listed salary. full_time / part_time / contract / permanent: filter by employment type. results_per_page: number of results per page (page size), default is set server-side by Adzuna if omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
whatNo
whereNo
companyNo
countryYes
sort_byNo
what_orNo
categoryNo
contractNo
distanceNo
locationNo
sort_dirNo
what_andNo
full_timeNo
part_timeNo
permanentNo
salary_maxNo
salary_minNo
title_onlyNo
what_phraseNo
max_days_oldNo
what_excludeNo
results_per_pageNo
salary_include_unknownNo
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full transparency burden. It discloses key behaviors: the AND vs OR matching semantics, silent zero-result failures for bad what and where values, and the default distance of 5km. It does not mention return format, pagination behavior, or rate limits, which would be useful but not strictly required for a read-only search.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured as a list of parameters, each earning its place with specific, actionable information. It is front-loaded with the purpose statement, and every line adds value without unnecessary fluff. The length is justified by the large parameter count.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers most parameters and provides important caveats, but it omits the return value structure, and a few parameters (page, company, max_days_old) are not described. Given the absence of an output schema, explaining what the tool returns would improve completeness. Overall, it is a strong description for a complex search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains nearly all 24 parameters, including nuanced distinctions among what, what_or, what_and, what_phrase, what_exclude, and title_only, and documents important behavioral caveats like silent failures and defaults. Only a few parameters (page, company, max_days_old) are left unexplained, which is a minor gap given the breadth covered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Search Adzuna's job listings,' which clearly identifies the action (search) and resource (Adzuna's job listings). It does not explicitly compare itself to sibling tools like salary_histogram or top_companies, so it lacks explicit differentiation for purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers internal parameter guidance, e.g., advising to use what_or instead of what for multi-word roles to avoid silent zero results, and references regional_data and list_categories for discovering valid values. However, it does not provide guidance on when to use search_jobs versus other sibling tools such as salary_histogram or top_companies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fabioba/mcp-adzuna'

If you have feedback or need assistance with the MCP directory API, please join our Discord server