Skip to main content
Glama

CyprusJobs.eu — jobs in Cyprus

Feed of vacancies posted by employers

vacancy_feed
Read-only

Full vacancies that employers posted on CyprusJobs.eu themselves (not copied from other sites), newest first, with description, pay, town and the link to apply; page through with offset. For job agents, aggregators and HR services that keep their own copy fresh. Needs an API key (free during our launch): https://cyprusjobs.eu/developers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vacancy_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoVacancies per page (default 50)
sinceNoOnly vacancies posted on or after this date, YYYY-MM-DD
offsetNoHow many to skip
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description does add genuinely new behavioral context: an API key is required and obtainable free at a given URL, and paging is offset-based. It stops short of covering rate limits, quota, or the response envelope.

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?

Scope and result contents are front-loaded in the first sentence, with audience, pagination and auth following in short clauses. It is dense but every sentence carries information; only the inline URL-with-pitch is slightly verbose.

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 no output schema, the description usefully enumerates the returned fields (description, pay, town, apply link) and covers auth and paging. Gaps remain around the language parameter and the response shape/last-page behavior, but the definition is sufficient to call the tool correctly.

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 75%, so most parameters are already documented, making 3 the baseline. The description only adds framing around 'offset' paging and 'newest first' ordering; it says nothing about the undocumented language enum or how 'since' interacts with ordering.

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 names a specific resource (vacancies posted directly by employers on CyprusJobs.eu), its scope ('not copied from other sites'), ordering ('newest first') and returned fields. It is unambiguous what the feed contains and how it differs from a search tool, though it never names a sibling like search_jobs 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?

The audience framing ('For job agents, aggregators and HR services that keep their own copy fresh') tells the agent this is a bulk-sync/full-feed tool rather than a targeted lookup. There are no explicit exclusions or named alternatives for one-off queries, which keeps it below a 5.

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