scrapewise_update_scraper_site_from_source
Builds the link list (Site) of ONE automation from the latest run of ANOTHER automation
of this account, on the server, and saves it. The call REPLACES the stored link list of
that automation (the same save as scrapewise_create_scraper_site with a fed list, but
you do not send the links: the server reads the source automation's latest results,
takes the chosen column, drops empty and repeated addresses and stores the rest).
Subject to the SITE_MAP plan feature.
The list is the one today's portal "Scraper-based links" dialog would save: the same
links, in the same order, with the same titles. A very big list can take minutes.
The call can outlive a 60-second tool timeout; the save still completes. Before you
retry, read the automation's site with scrapewise_get_scraper_site: when its
`lastBuild.requestId` equals your `buildRequestId`, that build ended (`outcome` OK, or
the refusal code and `message`). Retry with the SAME `buildRequestId` only for the same
build; a finished OK build is then returned without building again.
For a dedicated-endpoint automation the saved settings of that automation are added to
each link by the server (the portal adds unsaved panel values too; this call cannot).
Args:
- body (SiteBuildFromSourceDTO, required): `scraperId` (the automation that gets the
list), `linksSourceScraperId` (the automation whose latest results feed it),
optional `urlFieldName` / `titleFieldName` (result columns; omit the title for
empty titles), `updateLinksBySourceScraperAutomatically`,
`calculateCurlsAutomatically`, and `buildRequestId` (a new UUID per build). There
is no site id and no link list in the body.
Returns:
SiteBuildResultDTO: `site` (the saved SiteDTO with `linkCount`, `linksBuiltAt` and
`lastBuild`), `feedCounts` (rows read, rows with no usable address, collapsed rows,
repeated addresses, links built; null on a replay of a finished build) and
`linksDropped` (built links this automation cannot read; not stored).
Examples:
- Use when: "feed automation B from the product links automation A found" →
scraperId (B) + linksSourceScraperId (A) + urlFieldName
- Use when: the source run is large — the list never passes through your context
- Don't use when: you already hold the exact addresses → scrapewise_create_scraper_site
with `links`
- Don't use when: you want to create an automation for a list and run it → use
scrapewise_run_scraper_url_list
Error Handling:
- 400 FEED_BUILD_EMPTY: the source has no finished run, or no usable address in that
column; the existing list is kept.
- 400 FEED_LIST_TOO_LARGE: the source run holds more links than one automation may
feed another; the existing list is kept.
- 400 LINK_FEED_NONE_ADMISSIBLE / LINK_SOURCE_NOT_FOUND / validation errors (ids must
be automation ids, `buildRequestId` a UUID); nothing is changed.
- 409 BUILD_REQUEST_REUSED: that `buildRequestId` was used for a different build.
- 503 FEED_BUSY with Retry-After: another large link list is being prepared, or the
list is being updated from its source right now; nothing was changed — call again
after the Retry-After seconds.
- 402 if the plan lacks the SITE_MAP feature. 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": {
"body": "<body>"
},
"name": "scrapewise_update_scraper_site_from_source"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | `scraperId` (the automation that gets the list), `linksSourceScraperId` (the automation whose latest results feed it), optional `urlFieldName` / `titleFieldName` (result columns; omit the title for empty titles), `updateLinksBySourceScraperAutomatically`, `calculateCurlsAutomatically`, and `buildRequestId` (a new UUID per build). There is no site id and no link list in the body. |