scrapewise_create_scraper_site
A Site is the address list (link list) of ONE automation: the automation runs once
over every address on it. This endpoint creates or updates a Site by id (empty
body.id = create; set id = update). Subject to the SITE_MAP plan feature.
IMPORTANT: leaving out `id` creates a NEW Site on every call, but a scraper's run (and
scrapewise_get_scraper_site) reads only one Site per scraper — a list saved into a second
Site may never be scraped. Before saving, read the scraper's Site
(scrapewise_get_scraper_site) and send its `id`; omit `id` only when the scraper has no
Site yet, and make that first save on its own, not in parallel with another save for the
same scraper. For an API (cURL) scraper, send every link together with its `curl` in the
same save, unless the Site has `calculateCurlsAutomatically` on.
There are two ways to give an automation its addresses:
1. PASTED / UPLOADED list — send `links` (one {url, title} per address). The list
REPLACES the stored one. To add addresses, send the full new list.
2. FED list — set `linksSourceScraperId` (another automation of this account),
`urlFieldName` / `titleFieldName` (which of its result columns hold the address
and the title) and `updateLinksBySourceScraperAutomatically: true`; the list is
then refreshed from that automation's rows after every run of it. You do NOT
fetch those rows yourself and you never call a `/urls` endpoint — the server
copies them.
Storing a list turns the automation's list mode on by itself: no follow-up
scrapewise_create_scraper call is needed. To create an automation, attach a list
and run it in ONE call, use scrapewise_run_scraper_url_list instead.
Do NOT create one scraper per address — one automation holds the whole list.
Args:
- body (SiteDTO, required): the owning scraper (`scraperId`) and either `links`
(pasted list) or `linksSourceScraperId` + `urlFieldName` (fed list).
Returns:
The persisted SiteDTO including assigned id, and `linksDropped` (fed lists only:
how many offered addresses this automation cannot read and did not store).
Examples:
- Use when: "give automation {id} these 50 URLs" → scraperId + links
- Use when: "feed automation B from automation A's results" → scraperId (B) +
linksSourceScraperId (A) + urlFieldName
- Don't use when: you want to create an automation for a list and run it → use
scrapewise_run_scraper_url_list (one call)
- Don't use when: you want to add links to an existing site → there is no
add-links endpoint; re-PUT the full SiteDTO with the whole new list
Error Handling:
- 402 if customer plan lacks SITE_MAP feature.
- 400 if body validation fails.
- 400 if a PASTED link (no `linksSourceScraperId`) does not belong to this
scraper. A scraper that reads one kind of page runs its whole URL list
through that same reader, so every link must be a web address of that kind
and must carry everything that kind of read needs (for example the dates a
stay lookup needs, the postcode a store lookup needs, the type a trend
lookup needs). The message names the offending link and what is wrong with
it; nothing is guessed and nothing is silently dropped.
- A FED list (`linksSourceScraperId` set) is not refused whole: the links this
scraper can read are stored and the rest are DROPPED and COUNTED, on
`X-Links-Dropped` and on `linksDropped` in the body. A source column
legitimately carries addresses of other kinds, and one of them must not cost
the dependent scraper its whole list. 400 only when NOTHING offered is
readable — and then the previously stored list is kept untouched.
- 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_create_scraper_site"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | the owning scraper (`scraperId`) and either `links` (pasted list) or `linksSourceScraperId` + `urlFieldName` (fed list). |