Skip to main content
Glama

Google Jobs

google_jobs
Read-only

Search for job listings on Google Jobs. Returns job postings with titles, company names, locations, descriptions, and apply links aggregated from multiple job boards.

Each job has a job_id. Pass it to google_jobs_listing for the employer's ratings on review sites and the employer's website.

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

Input Schema

NameRequiredDescriptionDefault
qYesJob search query (e.g., 'software engineer', 'data scientist in New York'). Required.
glNoCountry code for search context (e.g., 'us', 'gb'). Defaults to the country of `location`, otherwise us. Some countries return results in their local language.
pageNoDeprecated. Use `next_page_token` to request the next page.
latitudeNoLatitude of the search location, in decimal degrees (-90 to 90). Use with `longitude`. Cannot be combined with `location`.
locationNoLocation for job search (e.g., 'San Francisco, CA', 'London, United Kingdom').
longitudeNoLongitude of the search location, in decimal degrees (-180 to 180). Use with `latitude`. Cannot be combined with `location`.
next_page_tokenNoToken from `pagination.next_page_token` in the previous response. Retains the original search location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / gl / description
      Previous value: -"Country code for search context (e.g., 'us', 'gb'). Default: us."New value: +"Country code for search context (e.g., 'us', 'gb'). Defaults to the country of `location`, otherwise us. Some countries return results in their local language."
  2. Changed4 schema fields changed
    • addedInput schema / properties / latitude
      Added value: +{
      +  "description": "Latitude of the search location, in decimal degrees (-90 to 90). Use with `longitude`. Cannot be combined with `location`.",
      +  "type": "number"
      +}
    • addedInput schema / properties / longitude
      Added value: +{
      +  "description": "Longitude of the search location, in decimal degrees (-180 to 180). Use with `latitude`. Cannot be combined with `location`.",
      +  "type": "number"
      +}
    • addedInput schema / properties / next_page_token
      Added value: +{
      +  "description": "Token from `pagination.next_page_token` in the previous response. Retains the original search location.",
      +  "type": "string"
      +}
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination. Default: 1."New value: +"Deprecated. Use `next_page_token` to request the next page."
  3. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the aggregation source ('aggregated from multiple job boards') and the cross-tool handoff via `job_id`, but it says nothing about result volume, latency, or regional-language effects flagged in the `gl` param.

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?

Two tight sentences with the purpose front-loaded and the workflow hint second. Nothing is redundant or padded, and the returned-field list earns its place by telling the agent what it gets back absent an output 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?

For a read-only search tool with no output schema, the description adequately covers both what comes back and how to chain to google_jobs_listing, while pagination and location modes live in the schema. Minor gaps are page-size expectations and how many results to anticipate, which matter for a multi-page search.

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%, so every parameter including the deprecated `page`, coordinate/location exclusivity, and `next_page_token` semantics is already documented in the schema. The description adds no parameter-level meaning and only references `job_id`, which is an output field rather than an input.

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 ('Search for job listings on Google Jobs') and immediately enumerates the returned fields (titles, companies, locations, descriptions, apply links). Job listings are clearly distinct from the other search/social sibling tools, so an agent can select it without ambiguity.

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?

Provides a concrete follow-up path: capture `job_id` and pass it to google_jobs_listing for employer ratings and website. That gives clear contextual guidance on the next step, though it never states when to prefer this over a general web search sibling or any exclusion conditions.

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