Skip to main content
Glama
google-jobs-scraper

google-jobs-scraper

google_jobs_link

Generate a Google Jobs search URL for any query, location, country, and language so users can open job results directly in a browser. Returns a link only, with no API key or network request.

Instructions

Build the Google Jobs web page URL for a job search, for the user to open in a browser. Free, no API key, makes no network request.

It returns only a link, not job data: Google does not return job listings to plain
HTTP requests, so this server cannot read that page itself. Use start_job_search
when the listings are needed as data.

Args:
    query: job title, skill or company, e.g. "registered nurse".
    location: city, region or country, e.g. "Houston, TX". Empty = no location.
    country: 2-letter country Google searches from, e.g. "us", "gb", "de".
    language: Google language code, e.g. "en", "de", "ja".

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_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
countryNous
languageNoen
locationNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses that the tool is free, needs no API key, makes no network request, returns only a link, and explains why the server cannot fetch listings itself. It also describes what the arguments mean and how empty location behaves.

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?

The critical constraint (returns only a link) is front-loaded and the args list is scannable. There is mild redundancy between 'It returns only a link, not job data' and the following explanation that Google won't serve listings to plain HTTP requests, but the repetition is short and reinforces an easy-to-miss limitation.

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 URL-builder tool this is complete: it states cost/auth/network behavior, clarifies the return is a link (and an output schema exists anyway), documents every parameter with format hints, and routes the agent to the correct sibling for actual job data. Nothing needed 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?

Schema description coverage is 0%, so the description must compensate, and it does: all four parameters are documented with meaning and concrete examples ('registered nurse', 'Houston, TX', 'us'/'gb', 'en'/'de'), plus the non-obvious rule that empty location means no location filter. This adds real value beyond bare typed fields.

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?

The opening sentence names a specific action and resource: 'Build the Google Jobs web page URL for a job search.' It also immediately clarifies the output type ('for the user to open in a browser') and later contrasts itself with start_job_search, so an agent can distinguish it from siblings without reading any 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?

It gives a clear when-to-use condition (when the user needs a page to open in a browser) and an explicit when-not/alternative: 'Use start_job_search when the listings are needed as data.' The precondition that this returns no job data is stated up front, preventing misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools