Skip to main content
Glama

Adzuna

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.5/5.0
Behavior4/5

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

Adds context beyond annotations: key-value scoping by identifier, persistence differences (authenticated vs anonymous), and 24-hour retention for anonymous sessions. No contradiction with 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?

Four sentences, front-loaded with purpose, no redundancy. Every sentence adds value.

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 simple 2-param tool with no output schema, description covers storage semantics, persistence, and companion tools completely.

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?

Schema coverage is 100% with good descriptions. Description adds typical key naming conventions (e.g., 'subject_property', 'target_ticker'), enhancing understanding.

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?

Description specifies verb 'Save' and resource 'data', and distinguishes from sibling tools 'recall' and 'forget'.

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?

Explicitly says when to use ('when you discover something worth carrying forward') and mentions complementary tools (recall, forget), but no explicit when-not-to-use.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Most tools are clearly distinct, but ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx_grounded and deep_research overlap with the base router, and the polymarket_* family contains several scanning/arbitrage tools with fuzzy boundaries. The long descriptions help, but an agent could easily call the wrong variant.

Naming Consistency3/5

There are coherent clusters (pipeworx_*, polymarket_*, ask_pipeworx_*, bare Adzuna verbs), but the overall server mixes snake_case, bare nouns, compound names, and -_prefixed names without a unifying convention. Some tools like compare_entities, entity_profile, and scan_dependency follow a descriptive style that does not match the verb_ noun pattern used elsewhere.

Tool Count2/5

37 tools is well above the 25-tool threshold, and the server named 'Adzuna' includes far more than job-search functionality: prediction markets, memory, subscriptions, npm dependency checks, AI visibility probes, and llms.txt generation. The count feels like a bundled mega-platform rather than a focused job-data server.

Completeness3/5

For a job-search-focused server, the Adzuna tools cover search, categories, history, regional stats, salary histograms, and top companies, but there is no direct job-detail or application workflow. For the broader Pipeworx research surface, coverage is very thorough, so the main completeness problem is the lack of a clear unified domain rather than a specific missing operation.

Resources