scrapewise_cancel_reapply_rules
Stops the run's active re-apply. A waiting job ends at once; a running one stops before its next batch
of rows (within a few seconds). Rows already written keep their new values — nothing is rolled back
and no column is removed. Calling it again, or on a run with no active re-apply, is harmless. Free
(no credits). Start it again later with scrapewise_run_reapply_rules: it continues safely, rows that
already have the new values are not written twice.
Args:
- jobId (string, path, required): the run's id (scraperJobStatusId).
Returns:
The latest job of the run with its state (CANCELLED once stopped, or still RUNNING for a moment
until the current batch ends); 204 No Content when the run never had a re-apply.
Examples:
- Use when: "stop re-applying the rules to run {jobId}".
- Don't use when: you want to stop a scrape → scrapewise_stop_scraper.
Error Handling:
- 400 (CustomerError) when the run does not exist for this customer.
- 401 Unauthorized; 500 INTERNAL.[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": "scrapewise_cancel_reapply_rules"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | Yes | the run's id (scraperJobStatusId). |