Skip to main content
Glama
google-jobs-scraper

google-jobs-scraper

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENNoYour Apify API token, needed for start_job_search and get_job_results. Without it, only the free google_jobs_link tool works.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
google_jobs_linkA

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".
start_job_searchA

Start a Google Jobs search and return a run_id immediately. Step 1 of 2: then call get_job_results(run_id) to get the listings (title, company, location, salary, posted date, full job description and the real apply URLs).

Starts the hosted Apify Actor "datalume/google-jobs-scraper" with your own Apify
account. Requires the APIFY_TOKEN environment variable. It is PAID per unique job
saved (current price: https://apify.com/datalume/google-jobs-scraper ); searches with
no results and blocked pages are not charged. Starting a search spends money even if
the results are never fetched, so start one only when the user wants job data. The
run stops at max_jobs and at max_total_charge_usd. Every query is searched in every
location; one search takes about a minute (19 Nov 2026: 59 s with "fast" coverage).

Args:
    queries: job titles, skills or companies, e.g. ["registered nurse"].
    locations: cities, regions or countries, e.g. ["Houston, TX"]. Empty = no location.
    country: 2-letter country Google searches from, e.g. "us", "gb", "de", "in".
    language: Google language code. Use the local language outside English-speaking countries.
    date_posted: "any", "today", "3days", "week" or "month".
    employment_type: "any", "fulltime", "parttime", "contract" or "internship" (English searches).
    remote_only: remote / work-from-home jobs only (English searches).
    coverage: requests per search: "fast" (3), "standard" (9) or "max" (13). More requests = more unique jobs and a longer run.
    max_jobs: stop after this many jobs in total. Keep small to control cost and response size.
    max_total_charge_usd: hard spending cap for this search, in USD.
get_job_resultsA

Get the jobs found by a search started with start_job_search. Step 2 of 2. Reading results is free; it never starts a new search.

Waits up to wait_secs for the search to finish. Returns {"finished", "status", "jobs",
"message"}. If "finished" is false the search is still running and "jobs" is empty:
call get_job_results again with the same run_id (do not start a new search).

Args:
    run_id: the run_id returned by start_job_search.
    wait_secs: how long to wait for the search to finish, 0-45 seconds.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool maps to a distinct step with no overlap: building a free browser link, starting a paid async search, and polling for results. Descriptions explicitly disambiguate the risky pair (google_jobs_link vs start_job_search) by telling the agent which to use when listings are needed as data.

Naming Consistency4/5

start_job_search and get_job_results follow a clean verb_noun pattern, and the two are explicitly labeled step 1/step 2. google_jobs_link deviates with a noun-style name rather than a verb, but it is still readable and semantically clear.

Tool Count5/5

Three tools is exactly the minimum surface for an async start/poll scraper plus a free link alternative. Each tool has a distinct role and none feels redundant or missing for this scope.

Completeness4/5

The start → poll lifecycle is fully covered, including wait_secs and cost caps, so an agent cannot hit a dead end while retrieving results. Minor gaps exist: no way to cancel an in-flight paid run or list prior runs, so stale run_ids must be tracked externally.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues