Skip to main content
Glama

Adzuna

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Categories

categories
Read-onlyIdempotent

Fetch Adzuna's normalized job-category list for a country (e.g. engineering, sales, healthcare) — returns tag slugs and display names. Use to enumerate valid category values before calling history or regional_stats with a category filter.

Input Schema

NameRequiredDescriptionDefault
countryYes

Output Schema

NameRequiredDescriptionDefault
resultsNo
__CLASS__No

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / __CLASS__
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / categories
      Removed value: -{
-  "description": "Job categories",
-  "items": {
-    "properties": {
-      "display_name": {
-        "description": "Category display name",
-        "type": "string"
-      },
-      "tag": {
-        "description": "Category tag identifier",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / results
      Added value: +{
+  "items": {
+    "properties": {
+      "__CLASS__": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "tag": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "gb"
+  },
+  {
+    "country": "us"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "categories": {
+      "description": "Job categories",
+      "items": {
+        "properties": {
+          "display_name": {
+            "description": "Category display name",
+            "type": "string"
+          },
+          "tag": {
+            "description": "Category tag identifier",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds context that the list is normalized, country-specific, and returns slugs/display names without contradicting the annotations.

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?

Two sentences, front-loaded action, and a targeted usage note. Every phrase contributes meaning.

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?

For a single-required-parameter tool with a rich annotation set and output schema, the description gives the essential behavior, return content, and downstream usage. Nothing critical is missing.

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?

With 0% schema description coverage, the description must carry parameter meaning. It clarifies that country selects the category list, but it doesn't specify format, allowed values, or defaults beyond what the schema examples (gb/us) already show.

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?

States a specific action ('Fetch Adzuna's normalized job-category list'), the resource ('for a country'), and the return shape ('tag slugs and display names'). It also differentiates itself from siblings by connecting to history and regional_stats.

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?

Provides explicit usage context: enumerate valid category values before calling history or regional_stats with a category filter. It doesn't spell out when-not-to-use or alternative category-listing tools, but the conditional is clear enough.

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

All Adzuna toolsInspect
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.

Resources