Skip to main content
Glama
google-jobs-scraper

google-jobs-scraper

get_job_results

Retrieve jobs found by a start_job_search run, waiting up to 45 seconds for completion; if unfinished, call again with the same run_id instead of starting a new search.

Instructions

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.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_job_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
wait_secsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses read-only/non-initiating semantics, that the call blocks for up to wait_secs, and that 'jobs' is empty while 'finished' is false. It does not say what happens on an invalid, expired, or already-consumed run_id, which is a meaningful omission for a polling tool.

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?

Front-loaded with purpose and workflow position, then the return shape, then the retry rule, then arg details - a sensible order. The parenthetical '(do not start a new search)' restates the earlier 'it never starts a new search', a small redundancy justified only as emphasis on a likely failure mode.

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?

No output schema exists, so the description supplies the return keys and interprets the 'finished'/'jobs' relationship, which is exactly what an agent needs to write a polling loop. Combined with the wait bound and retry instruction, nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: it gives the provenance of run_id (returned by start_job_search) and adds the 0-45 second bound on wait_secs, which the schema only shows as a default of 40 with no maximum. The default behavior when wait_secs is omitted is left implicit.

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 (get the jobs found by a search) and pins its position in a workflow with 'Step 2 of 2' plus the name of the tool that produces the run_id. The agent can distinguish it from start_job_search without opening either 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?

Explicit about the prerequisite (a run_id from start_job_search) and about the follow-up action: if 'finished' is false, call get_job_results again with the same run_id, not a new search. It also flags that reading is free, which removes a common hesitation about repeated polling calls.

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