scrapewise_update_matcher_schedule
Sets the schedule of the group's current matching setup, or clears it with a null body. It does NOT
start a run and does not change the setup or its results (a PUT of the setup would replace the results
and run). A new or changed schedule starts from now: missed earlier times are not run.
Args:
- id (string, path, required): the group's id.
- idempotency_key (string, query): REQUIRED for AI-agent keys. A new value for each new change; the
same value only to retry that same change.
- body (MatcherScheduleDTO or null): type AFTER_SCRAPES (re-run after each scrape), DAILY, EVERY_N_DAYS
(intervalDays 1..366) or WEEKLY (daysOfWeek, at least one, e.g. ["MONDAY"]); calendar types need
time ("HH:mm", 24 h) and take zone (IANA id, default Europe/Tallinn). null = run once (clears it).
scheduledAutoMatches (optional): KEEP_ADD (default; delivered matches stay, new ones are added) or
REPLACE (each scheduled run replaces the matches). Scheduled runs always keep review decisions.
- 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. Required then
(409 TAKE_OVER_ACTIVE without it); leave it out otherwise.
Returns:
The MatcherJobDTO with schedule, lastScheduledRun, scheduleDueAt, nextRunAt and the new version.
Examples:
- Use when: "match group {id} every Monday at 06:00 Tallinn time" -> {"type":"WEEKLY",
"daysOfWeek":["MONDAY"],"time":"06:00","zone":"Europe/Tallinn"}.
- Use when: "stop the automatic matching of group {id}" -> body null.
- Don't use when: you want to change the setup itself -> scrapewise_update_matcher_job.
Error Handling:
- 400 IDEMPOTENCY_KEY_REQUIRED: an AI-agent key sent no idempotency_key. Nothing was changed.
- 400 (CustomerError): a bad schedule field (the message names it); 400 FIELD_INVALID: a bad
scheduledAutoMatches value.
- 404: the group has no matching setup yet, an unknown group, or another customer's group.
- 409: the setup was replaced by a save meanwhile — read it again and retry with a new key.
- 409 IDEMPOTENCY_IN_FLIGHT (an idempotency conflict): retry after a second.
- 409 TAKE_OVER_ACTIVE: this key's admin works in another customer's account — end Take Over or
send customerRef=<that customer's ref>.
- 429 OWNER_EDIT_RATE_LIMIT (owner of a group on the newer engine): more than 10 changes of this group
in 10 minutes; wait Retry-After seconds, then retry (the SAME idempotency_key may be reused).
- 401 Unauthorized; 403 for a read-only key or a plan without matching.
- 5xx: read the setup again (scrapewise_get_matcher_job) before retrying.
Nothing was changed in each. The answer's version is new: a save built from an earlier read is 409
VERSION_CHANGED (read again first).[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>",
"idempotency_key": "<idempotency_key>"
},
"name": "scrapewise_update_matcher_schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's id. | |
| body | No | type AFTER_SCRAPES (re-run after each scrape), DAILY, EVERY_N_DAYS (intervalDays 1..366) or WEEKLY (daysOfWeek, at least one, e.g. ["MONDAY"]); calendar types need time ("HH:mm", 24 h) and take zone (IANA id, default Europe/Tallinn). null = run once (clears it). | |
| customerRef | No | Admin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise. | |
| idempotency_key | Yes | Required for AI-agent keys: a new value per new change, the same value only to retry it. |