cancel_job
Stops a long job that a tool started. The job is marked CANCELLED at once and its scrape runs
are asked to stop; a run that is in the middle of a page finishes that page first. The answer
says `stopping: true` while a run is still stopping.
Rows collected before the cancel stay stored and stay charged - read them with the results
tool. Addresses that were never fetched are not charged. A cancelled job cannot be resumed;
send the original request again to start a new one.
Each account can run a limited number of jobs at the same time. The place of a cancelled job
becomes free only once its runs have really stopped, so a new job sent right after a cancel
may be refused as busy for a short time - wait and send it again.
Calling this tool twice is safe: the second call reports the same state.
Args:
- jobId (path, required): the job_id a tool returned.
Returns:
McpOutcomeCancelDTO: `jobId`, `status` (CANCELLED - or DONE / FAILED when the job had
already finished and there was nothing to cancel), `stopping` (true while a run is still
stopping) and `costMicros` (what the job has cost so far, in micro-cents where
1 000 000 = 1 EUR).
Examples:
- Use when: the user changes their mind about a running job -> call with its jobId.
- Use when: a job costs more than the user agreed -> cancel it, then read what it collected.
- Don't use when: you only want to see how far the job is -> use the results tool.
- Don't use when: you want to stop an automation that was not started by a job -> use
scrapewise_stop_scraper.
Error Handling:
- 404 NotFound: no job with this job_id in this account (also for a malformed id).
- 403: the API key is read-only. A read-only key cannot start jobs, so it has none to cancel.
- 401 Unauthorized.[runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP outputSchema is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.
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": {
"jobId": "<jobId>"
},
"name": "cancel_job"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | Yes | the job_id a tool returned. |