scrapewise_get_match_evidence
Lists the product pairs of the group's latest finished matching run, 50 per page, with the matcher's own
stored fields for each pair, exactly as the matcher wrote them: its decision, basis, code and code kind, the
gates that fired, the deciding step / rule, every match line with its own name, level, score and result, the
signals and scores, and the review fields. Nothing is re-judged or renamed here. Read-only; costs nothing; a
Read key may call it.
Args:
- id (string, path, required): the group's id.
- page (integer, query, optional, default 0): the page, 50 pairs each.
- bucket (string, query, optional, default all): matched | review | no | all (by the stored decision).
- 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:
groupId, page, size (50), totalElements, totalPages and rows. Each row: pairId, link (the shop page, an
http(s) address or null) and stored: the matcher's fields as stored, for example matchDecision,
matchBasis, matchCode, matchCodeKind, gatesFired, decidedBy, matchLines, signals, signalCoverage,
totalScore, eanVerdict, matcherEngine, masterRef, reviewVerdict, reviewMasterRef, sourceName. A field
the matcher did not write is left out; a stored null is null; values the matcher adds later pass as
they are. No group run yet: rows is empty.
Examples:
- Use when: "why did these products match?", "which matches rest on an EAN?", "show the review pairs".
- Don't use when: you want what the next run costs -> scrapewise_get_matcher_run_estimate; the run's
state -> scrapewise_get_matcher_config_status.
Error Handling:
- 400: page below 0, or an unknown bucket.
- 404: 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_match_evidence"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's id. | |
| page | No | the page, 50 pairs each. | |
| bucket | No | matched | review | no | all (by the stored decision). | |
| customerRef | No | Admin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise. |