Skip to main content
Glama

Adzuna Search

adzuna_search
Read-onlyIdempotent

"Find jobs / openings / roles / positions for [title] in [city]" / "remote [role] jobs" / "[language / framework] developer jobs" / "salary range for [role] in [country]", search live job postings via Adzuna (global job-board aggregator). Filters: country (gb/us/ca/de/fr/...), title query, location, distance, salary band, full-time/permanent, posted recency. Returns ranked listings with title, company, location, salary, posted date.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "what": "python developer",
      "where": "London",
      "country": "gb",
      "results_per_page": 25
    },
    "name": "adzuna_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page (default 1)
sortNodefault | hybrid | date | salary | relevance
whatNoFree-text query (title + description)
whereNoLocation (city, region)
countryYesgb, us, ca, de, fr, ...
distanceNoSearch radius from `where`, in km
full_timeNo
permanentNo
salary_maxNoUpper bound
salary_minNoLower bound, in local currency
what_phraseNoExact-phrase variant of `what`
max_days_oldNoRestrict to jobs posted in the last N days
results_per_pageNo1-50 (default 20)

Output Schema

NameRequiredDescriptionDefault
countNoTotal matching jobs
resultsNoList of job postings
mean_salaryNoMean salary for results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the agent knows this is a safe, repeatable, live-web read. The description adds that results are ranked and come from a global aggregator with per-country coverage, which is useful context. It says nothing about rate limits, API credentials, empty-result behavior, or coverage gaps in the '...' country list, so it only modestly exceeds the annotation baseline.

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

Conciseness3/5

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

The content is front-loaded, but the first half is a slash-heavy synonym pile ('jobs / openings / roles / positions') that repeats one concept four ways. The core statement of what the tool does arrives only in the second sentence, after the examples. It is informative but not tight.

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?

For a 13-parameter search tool with an output schema and full annotation coverage, the description supplies the key intents, the filter surface, and the shape of results, which is enough to call it correctly. The remaining gap is guidance on parameter interaction (e.g., what vs. what_phrase, page vs. results_per_page) and country coverage, which would round it out.

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

Parameters3/5

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

Schema description coverage is 85%, so the schema already explains nearly every parameter; baseline 3 applies. The description's filter list (country, title query, location, distance, salary band, full-time/permanent, posted recency) mostly restates the schema, though it does add a semantic grouping that helps an agent map user intent to parameters. It adds no syntax, currency, or enum detail beyond what the schema provides.

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 names a specific verb+resource ('search live job postings via Adzuna, a global job-board aggregator') and the concrete result (ranked listings with title, company, salary, posted date). The example query phrasings ('remote [role] jobs', 'salary range for [role] in [country]') further pin down scope. It stops short of explicitly distinguishing itself from siblings like adzuna_categories or adzuna_history, so it lands at 4 rather than 5.

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

Usage Guidelines4/5

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

The quoted query templates effectively communicate the situations this tool is for — keyword job search, remote-role search, tech-stack search, and salary benchmarking. That is clear contextual guidance. However, no exclusions or named alternatives (e.g., when to prefer adzuna_categories or adzuna_history) are given, so it is not a full when/when-not treatment.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.