scrapewise_get_column_quality
Counts how many products share an ID value in a column, so you can tell whether a column can be used as
the group's ID column before a match run spends an hour on it. The ID column is what the matcher tells
two products apart by: when two products carry the same value, saved decisions and kept matches cannot be
told apart, and a run can be stopped by its own check for exactly that reason.
Read only. It costs nothing, changes nothing and starts no run; a Read key may call it. Counts only, never
a product's own values. Counts are computed over the trimmed, lower-cased value, which is what the matcher
itself compares, so `duplicated` is what would really collide.
Args:
- id (string, path, required): the group's id.
- body (required): {entries: [{jobId, column}]} - the main list's run and each connected shop's run in
one call, at most 512 entries. jobId values come from scrapewise_get_matcher_scope_jobs or
scrapewise_get_matcher_job (the saved scope).
Returns:
A bare JSON array of {jobId, column, total, empty, distinct, duplicated, tooLarge}. `total` = products
in that run, `empty` = products with no value, `distinct` = different values, `duplicated` = products
whose value another product also has. A column with duplicated 0 and a low `empty` is one you can use.
tooLarge=true with null counts = that run is over the 500,000-row cap and was not counted; read the last
run's own numbers from scrapewise_get_matcher_history instead.
An entry is LEFT OUT of the array when its jobId is unknown or belongs to another customer, or when the
column cannot be checked. The answer can even be empty for a whole group, because a scraper that
declares no columns of its own offers none here. A missing entry never means "the column is fine": it
means this call could say nothing about it.
Examples:
- Use when: "is the EAN column unique in group {id}?" before saving it as the ID column.
- Use when: a run was stopped because products share an ID value, and you need to say which column to
use instead.
- Don't use when: you want the match result itself -> scrapewise_get_matched_data; or the reason a run
was stopped -> scrapewise_get_matcher_history.
Error Handling:
- 400 (CustomerError): no group with this id for this customer, or more than 512 entries. Nothing was
counted.
- 429: too many uncounted checks for this customer in one minute, or too many running at once. Wait a
minute and ask again with the same body; a repeat of the same question is served from the cache and
costs nothing.
- 402 without the text-matching feature; 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>",
"body": "<body>"
},
"name": "scrapewise_get_column_quality"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's id. | |
| body | Yes | {entries: [{jobId, column}]} - the main list's run and each connected shop's run in one call, at most 512 entries. jobId values come from scrapewise_get_matcher_scope_jobs or scrapewise_get_matcher_job (the saved scope). |