Skip to main content
Glama

google: Google Jobs results

google_jobs
Read-only

Google Jobs results. Job postings for a query: title, company, location and the board it was syndicated from. Results lean toward an area that can change between calls, so name the place in your query. Slower than most endpoints, often 20 seconds or more. A failed attempt returns upstream_unavailable and is not charged. Costs 5 credits.

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>"
    },
    "name": "google_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
glNoTwo-letter country code Google should bias results toward.
hlNoHost language for the results page, e.g. "en", "de". Defaults to "en".en
tldNoGoogle marketplace TLD. One of: com, co.uk, ca, de, es, fr, it, co.jp, in, cn, com.sg, com.mx, ae, com.br, nl, com.au, com.tr, sa, se, pl. Defaults to "com".com
uuleNoNot currently supported; any value returns `invalid_request`.
queryYesSearch query
startNoNot currently supported; any value returns `invalid_request`.
country_codeNoTwo-letter country code. Sets `gl` when `gl` is not given.
cache_max_ageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / start / description
      Previous value: -"0-based result offset."New value: +"Not currently supported; any value returns `invalid_request`."
    • changedInput schema / properties / uule / description
      Previous value: -"Encoded Google location string for precise geo-targeting."New value: +"Not currently supported; any value returns `invalid_request`."
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

The description goes well past the readOnlyHint/openWorldHint annotations by disclosing latency ('often 20 seconds or more'), the failure mode and its billing consequence ('upstream_unavailable' and not charged), and a concrete cost of 5 credits. Those are exactly the operational facts an agent needs before committing a call.

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 short sentences, output shape first, then query advice, then latency, then error/billing. Every sentence carries information an agent would otherwise have to discover empirically; nothing is redundant with the schema.

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 correctly names the returned fields, and it covers cost, latency, and the primary failure mode for an eight-parameter tool. The only gap is caching behavior, since cache_max_age is the one parameter with no description anywhere.

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 88%, so the schema already documents gl, hl, tld, and the unsupported uule/start. The description only adds the practical hint that location should be expressed inside the query rather than relying on implicit bias, which is real but marginal value.

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?

States a specific resource and shape: 'Job postings for a query: title, company, location and the board it was syndicated from.' That is clearly distinct from general-purpose siblings like google_search or google_news. It stops short of naming a sibling it is not, which is what separates a 5 from a 4.

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?

It gives query-construction guidance ('name the place in your query') because results are area-biased and drift between calls, which is genuinely useful context. But there is no explicit when-to-use/when-not guidance and no routing to google_search for non-job queries, so the agent must infer the boundary.

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.