Adzuna

Search

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.

Input Schema

Name	Required	Description
`page`	No	1-based page (default 1)
`sort`	No	default \| hybrid \| date \| salary \| relevance
`what`	No	Free-text query (title + description)
`where`	No	Location (city, region)
`country`	Yes	gb, us, ca, de, fr, ...
`distance`	No	Search radius from `where`, in km
`full_time`	No
`permanent`	No
`salary_max`	No	Upper bound
`salary_min`	No	Lower bound, in local currency
`what_phrase`	No	Exact-phrase variant of `what`
`max_days_old`	No	Restrict to jobs posted in the last N days
`results_per_page`	No	1-50 (default 20)

Output Schema

Name	Required	Description
`count`	No	Total matching jobs
`results`	No	List of job postings
`mean_salary`	No	Mean salary for results

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "country": "gb",
+    "results_per_page": 25,
+    "what": "python developer",
+    "where": "London"
+  },
+  {
+    "country": "us",
+    "full_time": true,
+    "salary_min": 120000,
+    "sort": "salary",
+    "what_phrase": "senior software engineer",
+    "where": "San Francisco"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total matching jobs",
+      "type": "number"
+    },
+    "mean_salary": {
+      "description": "Mean salary for results",
+      "type": "number"
+    },
+    "results": {
+      "description": "List of job postings",
+      "items": {
+        "properties": {
+          "company": {
+            "properties": {
+              "display_name": {
+                "description": "Company name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "created": {
+            "description": "Creation timestamp",
+            "type": "string"
+          },
+          "description": {
+            "description": "Job description",
+            "type": "string"
+          },
+          "id": {
+            "description": "Job ID",
+            "type": "string"
+          },
+          "location": {
+            "properties": {
+              "display_name": {
+                "description": "Location",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "redirect_url": {
+            "description": "Job posting URL",
+            "type": "string"
+          },
+          "salary_currency": {
+            "description": "Currency code",
+            "type": "string"
+          },
+          "salary_max": {
+            "description": "Maximum salary",
+            "type": "number"
+          },
+          "salary_min": {
+            "description": "Minimum salary",
+            "type": "number"
+          },
+          "title": {
+            "description": "Job title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses that the tool searches live job postings from a specific aggregator (Adzuna) and returns ranked listings with key fields. This adds useful behavioral context beyond the annotations, such as the return format.

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 a single paragraph, well-structured with examples first, then source and filters, then output. It is efficient but slightly lengthy. Front-loading examples is effective.

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?

Given the high schema coverage and existence of an output schema, the description is sufficiently complete. It covers the main use case and key filters, though it omits details on pagination and sorting behavior.

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 coverage is high (85%), so the description adds marginal value. While it lists filter categories and provides examples, it does not elaborate on individual parameters beyond what the schema already describes.

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 for jobs with specific examples and identifies the data source (Adzuna). It uses specific verbs and resources, making the purpose unambiguous.

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 description provides concrete usage examples and lists available filters, guiding the agent on how to use the tool effectively. However, it does not explicitly contrast with sibling tools like 'search_within'.

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

All Adzuna tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.