scrapewise_get_matcher_review_ids
Lists the product pairs of a group's matching that still wait for a person's decision (the Review tab),
as ids in the chosen order, optionally one page at a time. Read-only; costs nothing; a Read key may call it.
Fetch the pairs themselves with scrapewise_get_matcher_review_pairs.
Args:
- id (string, path, required): the group's id.
- configId (string, path, required): the review key of the group's matching setup
(masterData.configId from scrapewise_get_matcher_job).
- sort (string, query, optional, default total): total = the matcher's total score, highest first; name =
the name score; photo = the photo score; desc = the photo description score; step1..step5 = one step's
score (newer engine); ai = the AI first review order: pairs the AI has checked first, most likely the
same product first, then the rest in total order (needs the AI review switched on for the group; without
it the order is total). Case-insensitive; unscored pairs come last.
- sources (string, query, optional): comma list of up to 100 source scraper ids; only their pairs.
- offset, limit (integer, query, optional): one page of the list (limit 1 to 10000) plus total.
- 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:
snapshotTs, ids (pair ids in order), keys (the stable pair keys, same order), total (paged calls only),
steps (newer-engine groups: the configured steps and their lines).
Examples:
- Use when: "which pairs of group {id} should I check first?" -> sort=ai, limit=20.
- Use when: walking the whole review list page by page -> offset/limit.
- Don't use when: you want why pairs matched -> scrapewise_get_match_evidence.
Error Handling:
- 400: an unknown sort, a bad sources value or a bad offset / limit.
- 404: unknown group, another customer's group or a configId that is not this group's.
- 409: the list cannot be filtered by source right now (show all, retry shortly); TAKE_OVER_ACTIVE.
- 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>"
},
"name": "scrapewise_get_matcher_review_ids"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's id. | |
| sort | No | total (default), name, photo, desc, step1..step5 or ai (the AI first review order) | |
| limit | No | Page size, 1 to 10000; absent with no offset = the whole list | |
| offset | No | Page start in the not-yet-decided list (0 or more); with limit | |
| sources | No | Comma-separated source scraper ids (24-hex, at most 100) to focus on | |
| configId | Yes | the review key of the group's matching setup (masterData.configId from scrapewise_get_matcher_job). | |
| customerRef | No | Admin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise. |