Skip to main content
Glama

Verifera job search

Search live jobs on Verifera

search_jobs
Read-onlyIdempotent

Searches live job adverts on Verifera's UK, US, Netherlands and Portugal job sites. Returns title, employer, place, pay text, date posted and a link to the advert's page on Verifera, where a person can read the full advert and apply. The fields are advert data supplied by employers and job boards.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "country": "<country>"
    },
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesJob title or keywords, for example 'staff nurse'.
cursorNoThe next_cursor of a previous result, to get the next page of the same search.
remoteNoOnly remote adverts when true.
countryYesWhich job site: GB, US, NL or PT.
locationNoTown, city or area.
salary_minNoMinimum advertised salary, in the site's own currency.
posted_within_daysNoOnly adverts posted within this many days. Rounded up to 1, 3, 7 or 14; 14 is the longest window and is used when this is left out.

Output Schema

NameRequiredDescriptionDefault
jobsYes
noticeNo
countryYes
next_cursorYesPass as cursor for the next page; empty when there is no further page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: results are pointers to advert pages rather than the adverts themselves, and "the fields are advert data supplied by employers and job boards" warns the agent about provenance/accuracy of the content. Pagination behavior is left entirely to the cursor parameter's schema description.

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?

Three sentences, front-loaded with purpose and coverage before the return fields and the provenance caveat. No filler or restated title text; every sentence contributes. Slightly dense in the second sentence but still readable.

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?

With an output schema present, the description doesn't need to explain return values, and annotations cover the safety profile. What remains is well covered: markets, result shape, and a data-quality caveat. It doesn't mention result caps or rate limits, but nothing in the context signals those are a concern.

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 description coverage is 100%, including the enum for country, the cap on posted_within_days, currency semantics for salary_min and the cursor's next-page role, so the schema carries the parameter burden. The description adds nothing about parameters — notably it doesn't restate that results cover multiple sites/currencies, which is only visible via salary_min's schema note. Baseline 3 applies.

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?

The description opens with a specific verb and resource ("Searches live job adverts") and names the covered markets (UK, US, Netherlands, Portugal). It also enumerates what comes back (title, employer, place, pay text, date posted, link), so the agent knows exactly what kind of result to expect. No siblings exist to differentiate against, which is the only thing keeping it from a 5.

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?

Usage is implied rather than stated: the note that the tool returns "a link to the advert's page on Verifera, where a person can read the full advert and apply" signals this is a discovery/search tool, not a source of full advert text. There are no explicit when-to-use or when-not-to-use instructions, and none of the filtering parameters are framed as recommended defaults.

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.

Resources