scrapewise_run_scraper_url_list
Creates ONE automation for a list of web addresses of one kind (for example 300 Amazon
product pages, or 50 Google News searches), stores the whole list as its link list, and
starts ONE run over all of them — in a single call. Do NOT create one scraper per address
or loop scrapewise_create_scraper / scrapewise_run_scraper over a list: that creates
hundreds of automations, each billed and scheduled on its own.
The run has no time limit: it stops only when the list is done, the wallet is empty, or the
user stops it. A website-emails list (endpoint websitecontacts) stops after the job-time
limit (23 hours by default): its job then says stoppedReason TIME_LIMIT and paused true,
nothing unread is charged, and scrapewise_run_scraper with continueFromJobId continues it
with only the websites not read yet. Rows appear under the returned scraperId as the run
progresses.
Billing: a resume (`rerun: true`) charges only the addresses that were never attempted. A
force (`force: true`) charges every address again. Neither ever charges an address twice
inside one run.
If an automation with this name already exists in this group, its stored address list is
replaced only if you send its `scraperId`; otherwise the call is refused.
When retrying a failed call, send the exact same `name`. A different name over the same
addresses creates a second automation and charges every address again.
Args:
- groupId (string, required): the group (folder) the automation belongs to — from
scrapewise_get_scraper_group_list.
- name (string, required, ≤ 200 characters): the automation's name.
- urls (array of strings, required, 1-5000): the addresses, all of the kind one
endpoint reads. Duplicates are collapsed and never charged twice. More than 5000:
upload the list as JSON Lines instead (REST only, same path,
Content-Type: application/x-ndjson; first line
{"groupId","name","clientRequestId"}, then one {"url","title"} per line).
- endpointTag (string, optional): the endpoint (e.g. gnews, amazonsearch); detected
from the first address when omitted. idealo addresses are never detected: send
idealooffers (every shop's price, one row per shop, for idealo product pages or
idealo search links with ?q=<EAN> — e.g. every shop's price for 500 EANs on
idealo.de) or idealosearch (search / category pages). Not affiliated with idealo.
- scraperId (string, optional): an existing automation whose list this one replaces.
- rerun (boolean, optional): continue a list that did not finish — only the addresses
never attempted are fetched and charged.
- force (boolean, optional): scrape the whole list again and pay for it again.
Returns:
BulkUrlRunResultDTO: scraperId, groupId, tag, linksAccepted, linksDropped (always 0
here), linksQueued (addresses this run will fetch), resumedFrom (on a resume),
maxExpectedRows (one row per address endpoints; null for list-shaped ones such as a
news search), estimatedMicroCents (upper bound: linksQueued × maxRequestsPerLink ×
price per request; null when unknown), maxRequestsPerLink (most billed requests per
address: 3 for website contacts, else null), jobQueued, reused (an existing automation
was used), runSkippedReason (NOTHING_TO_RESUME when a resume had nothing left).
Examples:
- Use when: "scrape these 200 Amazon product pages" → one call, name + the 200 urls
- Use when: "run these 40 news searches every day" → one call; schedule it afterwards
- Use when: a call failed and you retry → the SAME name and urls
- Don't use when: you want one page previewed → use scrapewise_get_scraper_sample_data
- Don't use when: the automation already exists and you only want to run it again as it
is → use scrapewise_run_scraper with its id
Error Handling:
- 400 INVALID_URL: an address cannot be used — it is named (line + address); nothing
was saved. Fix or remove it and send the list again.
- 400 LIST_TOO_LARGE: more than 5000 addresses — use the JSON Lines upload.
- 400 TAG_NOT_RESOLVED / TAG_NOT_SUPPORTED: the addresses are not of one kind this
route runs; send endpointTag or a list of one supported kind.
- 402: the wallet has no balance and no free requests.
- 404 GROUP_NOT_FOUND: the group is not in this account.
- 409 PREVIOUS_RUN_ALREADY_CHARGED / PREVIOUS_RUN_TRUNCATED: this list was already
run and charged. The body carries rowsAlreadyStored and `options` — what `rerun`
and `force` would queue and cost. Read the stored rows, or send rerun / force.
- 409 NAME_TAKEN_WITH_DIFFERENT_LIST: another list lives under this name; send its
scraperId to replace it, or a different name.
- 409 AMBIGUOUS_SCRAPER_NAME: two automations share this name; send scraperId.
- 409 LIST_RESUME_OFF: a website email list cannot be continued right now; nothing
was saved or started.
- 409 ALREADY_RUNNING / BULK_RUN_IN_PROGRESS / BULK_RUN_LEASE_HELD: a run of this
list is still going; wait (Retry-After) and send the same request again.
- 413: the request body is larger than 12 MB.
- 429 INGEST_CAPACITY / INGEST_CAPACITY_CUSTOMER / INGEST_CAPACITY_GLOBAL: too many
uploads at once; retry after Retry-After.
- 401 Unauthorized; 403 for a read-only API key.[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_run_scraper_url_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | The automation to create and run: groupId, name and urls (1 to 5000 addresses of one kind), plus the optional fields listed in this tool's description. |