Provided by DataForSEO
SERP google jobs task
Google jobs via a DataForSEO SERP task: one native task per Run, submitted once, completed by the vendor's pingback and read from task_get through a durable Provider Job. Priced by the vendor's task fee for up to 10 results; an empty result set is reported as no result.
Contract snapshot: 2026-09-17. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"keyword",
"location_code",
"language_code"
],
"properties": {
"depth": {
"type": "integer",
"maximum": 10,
"minimum": 1
},
"keyword": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"language_code": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"location_code": {
"type": "integer"
},
"employment_type": {
"type": "array",
"items": {
"type": "string",
"maxLength": 2048,
"minLength": 1
},
"maxItems": 100,
"minItems": 1
},
"location_radius": {
"type": "string",
"maxLength": 2048,
"minLength": 1
}
},
"additionalProperties": false
}{
"keyword": ".net developer",
"language_code": "en",
"location_code": 2840
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How to run it
Two fields identify it: the Provider and the endpoint key. The key looks like a path because it usually mirrors the Provider's own, but it is an opaque identifier — not a URL you can open. The same provider:endpoint pair is what your Policy lists.
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.mdThen ask for this Endpoint:
Run the DataForSEO Endpoint /v3/serp/google/jobs/task_post on Glasser with input {"keyword":".net developer","language_code":"en","location_code":2840}glasser run -p dataforseo -e '/v3/serp/google/jobs/task_post' -i '{"keyword":".net developer","language_code":"en","location_code":2840}' --endpoint-version 1Pinned to version 1, the one this page shows: if a newer version is published first, the Run is refused instead of charged under new terms. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"dataforseo","endpoint":"/v3/serp/google/jobs/task_post","input":{"keyword":".net developer","language_code":"en","location_code":2840},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Pinned to version 1 for the same reason as the CLI.
What each outcome charges
| No result | The Provider answered: nothing matched. | $0.0006 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |