google-jobs-scraper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | No | Your 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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). |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.