scrapewise_update_scraper_group_price_monitor_pick
Pins ONE listing as ours under one pairing-column value, for the cases where the data
cannot tell: several of our own rows carry the same value, so the comparison would
otherwise have to guess which is the product we sell. A confidently wrong price on a
pricing screen is worse than an empty cell, so the tool asks instead of guessing.
Idempotent by key — answering again for the same key REPLACES the previous answer rather
than accumulating, because a person can only mean one listing at a time.
Both the key and the name travel in the BODY and never in the path. When the pairing
column is a product title the key is arbitrary customer text containing `/`, `#`, `%` and
spaces; even percent-encoded, a proxy or path matcher can decode `%2F` early and route the
request elsewhere.
Args:
- id (string, path param, required): the group's MongoDB ObjectId.
- body (GroupPickDTO, required): key (the pairing-column value exactly as scraped,
1-512 chars) and name (product name of the listing that is ours, 1-512 chars).
Returns:
The group's full pick map after the write, same shape as GET .../picks.
Examples:
- Use when: "under EAN 4741243009332 the one we sell is 'Varikatus LEGEND 3x4m'".
- Don't use when: the pairing column is simply the wrong column — fix that on
PUT /group/{id}/price-monitor instead of pinning thousands of rows by hand.
Error Handling:
- 400 (CustomerError envelope) if no such group for this customer, or if the group
already holds the maximum of 5000 picks (which means the pairing column is not
identifying products).
- 400 if key or name is blank or longer than 512 characters.
- 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_pick"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's MongoDB ObjectId. | |
| body | Yes | Names which listing under a pairing-column value is the customer's own. |