scrapewise_get_matcher_history
Lists the group's matching runs and stored drafts, newest first: one row per run that finished,
failed or was stopped (kept even after a later save replaced it), plus the live job while it is a
draft or still running. Each row carries the full setup that run used, so an earlier setup can be
read here and saved again with scrapewise_update_matcher_job. Read-only; costs nothing.
Args:
- id (string, path, required): the group's id.
- withDeleted (boolean, query, optional): true also lists runs hidden by "delete all matching
data". Default false.
- customerRef (string, query, optional): only for a Scrapewise admin key while the admin works in
another customer's account (Take Over): the customerUniqueRef of that customer. Required then
(409 TAKE_OVER_ACTIVE without it); leave it out otherwise.
Returns:
A list of MatcherJobDTO: id, status, masterData, scope, scopeScraperIdByJobId, created,
expectedRowCount (matched rows of a finished run), failureReason, configId, and on a finished
run of the newer engine setupSnapshot (setupSource db / file / default, activeVersion, setupHash:
two runs with the same setupHash ran the same setup). When run choices are on: runChoices {auto,
manual, requestedAt, startId, scheduled}, keptCount, keptDropped, verdictApply {applied, unapplied,
late}, ledgerStatus, and on a run that started fresh freshCutoffAt, freshCurrent (undo allowed),
freshUndone. Absent = not recorded.
Examples:
- Use when: "what did the last three matching runs of group {id} use?".
- Use when: restoring an earlier setup (read the row, swap in the newest run ids, save).
- Don't use when: you only need the current setup -> scrapewise_get_matcher_job.
Error Handling:
- 400 (CustomerError): no group with this id for this customer.
- 409 TAKE_OVER_ACTIVE: this key's admin works in another customer's account — end Take Over or
send customerRef=<that customer's ref>.
- 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": {
"id": "<id>"
},
"name": "scrapewise_get_matcher_history"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's id. | |
| customerRef | No | Admin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise. | |
| withDeleted | No | true also lists runs hidden by "delete all matching data". Default false. |