scrapewise_update_scraper_group_price_monitor
Records which scraper in the group is the customer's OWN, how a row is paired with a
competitor's row, and which columns hold the price and the product label. All fields are
applied as sent; null clears that one choice back to "let the portal auto-pick".
Group-scoped rather than per-user because this describes the group's DATA, not a personal
preference: a group is one collection with its own customer-defined column names, and the
answer to "which column is the price" is the same answer for every colleague. Kept in
browser storage it was per-person, so two people could open one group and be shown two
different prices for the same product.
Args:
- id (string, path param, required): the group's MongoDB ObjectId.
- body (GroupPriceMonitorDTO, required): me (the scraper NAME the customer owns),
mode ("matched" = product-matcher output, "title" = identical column value), key
(the column paired on when mode is not "matched"), price, productName, category
(top-level category column), subcategory, salePrice (discounted price shown
alongside price). Each nullable; null = auto-pick. `confirmedAt` in the body is
IGNORED — the server stamps it, because saving is what confirms. A column cannot
be reused across two of these roles (400 if it is).
Returns:
The updated GroupDTO, carrying priceMonitor with the server-stamped confirmedAt.
Examples:
- Use when: "in group {id} we are the scraper 'home4you', pair products on identical
`kood`, and the price is `hind`".
- Use when: "stop forcing a price column in group {id}, go back to auto" → price=null.
- Don't use when: you want to change a personal view/sort/filter — those are not
group data and are not stored here.
Error Handling:
- 400 (CustomerError envelope) if no group with the given id exists for this customer,
or if two of the settings name the same column.
- 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_update_scraper_group_price_monitor"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's MongoDB ObjectId. | |
| body | Yes | How a group's rows are read as a price comparison; null = portal auto-picks. |