scrapewise_create_scraper_group
Create-or-update by id semantics: empty `id` in the body creates a new group;
non-empty `id` updates the existing group with that id. Creating is
plan-feature gated by MAX_GROUPS limit; updating is not gated.
Args:
- body (GroupDTO, required): full group definition. Set `id` to update;
omit to create. Includes name, dataTable name, schedule, etc.
Returns:
The persisted GroupDTO including the (possibly newly assigned) id and
server-stamped fields.
Examples:
- Use when: "create a new group called 'türklased'" → body with id omitted
- Use when: "rename group {id} to 'X'" → body with id set + new name
- Don't use when: you want to delete → use scrapewise_delete_scraper_group
Error Handling:
- 402 if customer plan's MAX_GROUPS limit is reached on a create.
- 400 if body validation fails.
- 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": {
"body": "<body>"
},
"name": "scrapewise_create_scraper_group"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | full group definition. Set `id` to update; omit to create. Includes name, dataTable name, schedule, etc. |