Skip to main content
Glama

Search UK Jobs

jobs.reed.search
Read-onlyIdempotent

Search UK job listings — filter by keywords, location, distance, salary range (GBP), contract type (permanent/contract/temp), full/part time. Returns title, company, salary, applications count, direct link. UK largest job board (Reed.co.uk)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination (must be divisible by limit)
limitNoMax results (1-100, default 25)
contractNoFilter contract positions only
distanceNoSearch radius in miles from location (default 10)
keywordsNoJob search keywords (e.g. "python developer", "data scientist", "nurse")
locationNoUK location — city, town, or postcode (e.g. "London", "Manchester", "SW1A 1AA")
full_timeNoFilter full-time positions only
part_timeNoFilter part-time positions only
permanentNoFilter permanent positions only
salary_maxNoMaximum annual salary in GBP (e.g. 80000)
salary_minNoMinimum annual salary in GBP (e.g. 30000)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds that the tool returns specific fields (title, company, salary, applications count, direct link) but does not contradict annotations. No further behavioral traits are disclosed.

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?

The description is a single, well-structured sentence that front-loads the core action ('Search UK job listings') and lists filters concisely. Every part contributes information without redundancy or fluff.

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 complexity (11 parameters, output schema exists), the description covers the main purpose, filters, return fields, and source. It does not mention pagination or defaults, but these are documented in the schema. Overall, it is fairly complete for a search 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?

The input schema has 100% description coverage for all 11 parameters, so the description adds no additional meaning beyond what the schema already provides. The description enumerates filter categories but does not elaborate on individual parameter details.

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 'Search UK job listings' and enumerates specific filters (keywords, location, distance, salary range, contract type, full/part time). It further distinguishes from sibling tools by naming the source 'UK largest job board (Reed.co.uk)'. This provides a specific verb+resource+scope.

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

Usage Guidelines3/5

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

The description implies usage for UK-specific job searches on Reed.co.uk, but does not explicitly state when to use this tool versus alternatives like jobs.adzuna.search or jobs.jooble.search. No exclusion criteria or contextual triggers are 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.