Skip to main content
Glama

WhatJobs Job Search

Compare job counts

compare_job_counts
Read-only

Compare how many jobs are live on WhatJobs right now across places and/or roles.

Use this when the user asks where the most jobs are, how much demand there is, or to compare cities or roles, e.g. "Where are the most data analyst jobs in Germany?", "More jobs for nurses or carers in Leeds?", "Paris vs Berlin for developers".

Inputs:

  • keywords: one or more job roles (may be [""] to count all jobs).

  • locations: one or more places to search, not the user's own location unless they ask about jobs near them. Up to 6 keyword x location combinations are compared.

  • market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn.

Each row includes a link to that search on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

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": {
      "keywords": "<keywords>",
      "locations": "<locations>"
    },
    "name": "compare_job_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNo
keywordsYes
locationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses the 6-combination cap, the market default behavior (each location uses its own country), the WhatJobs-only data source, attribution requirements, and the fallback message when a country's listings are unavailable. This is rich behavioral context that annotations alone do not provide.

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?

Front-loaded with purpose and usage, then structured inputs. The long enumerated market list is bulky but functional; otherwise there is little waste.

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 3-parameter tool with no output schema, the description covers inputs, defaults, result shape (each row includes a link), data provenance, and edge-case behavior. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the full burden and does so: it explains keywords (including the [""] all-jobs case), locations (and the caveat about the user's own location), and market (optional, default empty, with the full supported value list). This meaningfully exceeds what the bare schema conveys.

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 verb and resource ('Compare how many jobs are live on WhatJobs right now across places and/or roles'), which is clearly distinct from siblings like search_jobs or compare_salaries. An agent can identify the tool's function without opening the schema.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('where the most jobs are, how much demand there is, or to compare cities or roles') and backs that with three concrete example queries. The guidance is specific enough to route the agent correctly against alternatives.

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.