scrapewise_get_matcher_review_pairs
Returns the product pairs of a group's Review tab by id, up to 500 per call, with their scores and, when
asked, chosen columns of both products. Read-only; costs nothing; a Read key may call it. Get the ids from
scrapewise_get_matcher_review_ids first (sort=ai for the AI first review order).
Args:
- id (string, path, required): the group's id.
- configId (string, path, required): the review key of the group's matching setup.
- body (required): ids (1 to 500 pair ids); optional fields, leftFields, rightFields (column names to
show for the product and the main-list row, at most 40 each).
- 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.
Returns:
One entry per pair found: id, stablePairKey, matcherRunId, leftKey, rightKey, picture links, scores
(textScore, imageCosine, picScore, fusionScore, numberScore), status, the chosen columns (leftFields,
rightFields), lines and stepScores on newer-engine groups, and aiReview when the AI first review has
looked at the pair in the current run: status (done, pending, failed, invalid, skipped), and for done
verdict (SAME, DIFFERENT, UNSURE), matchProbability (0 to 1), reason (at most 25 words), agreeing lines
and conflicting values, each named by the setup's line key and its columns; photoText when it read the
photos. aiReview is advice only: it never changes a match. An unknown or foreign id is left out.
Examples:
- Use when: "show me the first 20 pairs to review and what the AI thinks" -> ids from review ids.
- Don't use when: you want to save a decision -> the portal Review tab.
Error Handling:
- 400: no ids, more than 500 ids or more than 40 fields.
- 404: unknown group, another customer's group or a configId that is not this group's.
- 409 TAKE_OVER_ACTIVE: end Take Over or send customerRef=<that customer's ref>.
- 401 Unauthorized; 429 RATE_LIMITED; 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>",
"configId": "<configId>",
"body": "<body>"
},
"name": "scrapewise_get_matcher_review_pairs"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's id. | |
| body | Yes | ids (1 to 500 pair ids); optional fields, leftFields, rightFields (column names to show for the product and the main-list row, at most 40 each). | |
| configId | Yes | the review key of the group's matching setup. | |
| customerRef | No | Admin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise. |