Skip to main content
Glama
soheilfallah

adzuna-mcp

by soheilfallah

adzuna_search_jobs

Read-onlyIdempotent

Search job ads by keyword, location, salary, and contract type. Get results with title, employer, salary range, and a link to the full ad.

Instructions

Search Adzuna's job advertisement database with keyword, location, salary and contract filters.

Returns ads including title, employer, location, salary range (annual, local currency), contract type, category, posting date and a redirect_url. Adzuna only returns a SNIPPET of each description — fetch the redirect_url to read the full ad.

Args: params (SearchJobsInput): Validated search parameters. Key fields: - country (str): ISO code, default 'gb' - what / what_or / what_and / what_phrase / what_exclude / title_only (Optional[str]): keyword filters - where (Optional[str]) + distance (Optional[int]): free-text location and radius in km - location0/1/2 (Optional[str]): hierarchical location filter - category (Optional[str]): tag from adzuna_list_categories - salary_min / salary_max (Optional[int]): annual salary bounds - full_time / part_time / permanent / contract (Optional[bool]): contract filters - max_days_old (Optional[int]), sort_by (Optional[SortBy]), page, results_per_page - response_format (ResponseFormat): 'markdown' or 'json'

Returns: str: Markdown summary of matching ads, or JSON with keys count (int, total matches), mean (float, mean salary) and results (list of job objects each containing id, title, description, created, redirect_url, salary_min, salary_max, salary_is_predicted, contract_type, contract_time, latitude, longitude, company{display_name}, location{display_name, area[]}, category{label, tag}). On failure, an 'Error: ...' string explaining the cause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations declare readOnlyHint and idempotentHint, which the description aligns with. The description adds behavioral details: returns only a snippet of descriptions, requiring fetching the redirect_url for full ads, and mentions error handling (returns 'Error: ...' string).

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

Conciseness4/5

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

The description is well-structured with a concise intro, bullet-point parameter list, and return value explanation. It is comprehensive but slightly lengthy; however, every sentence serves a purpose.

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

Completeness5/5

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

Given the tool's complexity (many optional filters, output schema exists), the description is complete. It covers input parameters, output format, failure mode, and a key behavioral note (snippet vs. full ad). No gaps found.

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

Parameters4/5

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

The description provides an Args section that explains each parameter's purpose, adding context beyond the schema descriptions. Though a few parameters like sort_direction and salary_include_unknown are omitted, the coverage is high and adds value (e.g., explaining keyword AND/OR semantics).

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

Purpose5/5

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

The description clearly states the tool searches Adzuna's job advertisement database with filters, and lists the fields returned. It distinguishes from sibling tools like adzuna_list_categories and adzuna_salary_histogram by its specific search function.

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 does not explicitly state when to use this tool versus alternatives, nor when not to use it. It implicitly references adzuna_list_categories for category selection but lacks direct usage guidance.

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/soheilfallah/adzuna-mcp'

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