Skip to main content
Glama

Adzuna History

adzuna_history
Read-onlyIdempotent

"Job market trends" / "hiring trends in [category]" / "salary trends for [role]" / "is [field] hiring more / less than last year", historical monthly time series for job volume and mean salary in a country, optionally filtered by location and category. Use for labor-market analysis, recession indicators, hiring-cycle research.

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": {
      "months": 24,
      "country": "gb"
    },
    "name": "adzuna_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNo1-100 (default 12)
countryYes
categoryNoAdzuna category tag (from `categories` tool)
locationNo

Output Schema

NameRequiredDescriptionDefault
monthNoAverage salary keyed by month, e.g. {"2026-07": 42537.34}. An OBJECT map, not an array, verified against a live response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / month / description
      Previous value: -"Average salary keyed by month, e.g. {\"2026-07\": 42537.34}. An OBJECT map, not an array — verified against a live response."New value: +"Average salary keyed by month, e.g. {\"2026-07\": 42537.34}. An OBJECT map, not an array, verified against a live response."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly/openWorld/idempotent and non-destructive, so safety is covered. The description adds that data is historical and monthly-granular, but says nothing about coverage limits, data lag, whether sparse categories return empty series, or rate limits on an open-world lookup.

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?

Front-loads the intent with quoted natural-language queries, then one dense sentence specifying the returned series and filters, then use cases. Slightly noisy with the four quoted phrasings, but every clause maps to a real capability.

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?

Returns are covered by an output schema, so the description needn't explain them, and it correctly states the core payload (monthly volume and mean salary). The remaining gap is country/location input formatting for a 4-parameter open-world tool.

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 50%, so the baseline is 3. The description confirms country as the geographic scope and location/category as optional filters, but adds no format guidance for the country field (the examples imply ISO codes like "gb"/"us") and nothing about accepted location strings.

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?

States a concrete verb+resource: "historical monthly time series for job volume and mean salary in a country," with the filtering dimensions named. It is clearly distinguishable from a live job search or a categories lookup, though it never names those siblings explicitly.

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?

Gives explicit when-to-use framing via the quoted example intents and the closing line "Use for labor-market analysis, recession indicators, hiring-cycle research." No when-not-use condition or named alternative (e.g. adzuna_search for current postings) is provided.

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.