scrapewise_update_scraper_fallback
Attaches a fallback scraper configuration to a SINGLE_PRODUCT scraper. The
fallback runs automatically when the primary scraper extracts no data for a
link — typically a backup parser for a sub-set of the same site or a different
extraction strategy. Requires the FALLBACK_SCRAPER plan feature.
Args:
- body (FallbackScraperCreateDTO, required):
- scraperId (string): id of the SINGLE_PRODUCT scraper to attach the
fallback to.
- fallback (ScraperDTO): the fallback scraper's configuration.
Returns:
The persisted ScraperDTO of the fallback (with id assigned), or null if the
attachment failed silently (rare; usually 4xx instead).
Examples:
- Use when: "give scraper {id} a fallback that uses JSON-LD instead of CSS"
- Don't use when: the primary scraper is MULTIPLE_PRODUCTS — fallbacks are
SINGLE_PRODUCT-only
Error Handling:
- 402 if customer plan lacks FALLBACK_SCRAPER feature.
- 400 if the primary scraper is not SINGLE_PRODUCT type.
- 400 (CustomerError envelope) if scraperId doesn't exist for this customer.
- 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": {
"body": "<body>"
},
"name": "scrapewise_update_scraper_fallback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Object with the fields scraperId, fallback. |