batch_operations
Run up to 50 save_page, save_component, save_chrome, save_entry, save_localization, or delete_entry calls in order. Not one transaction unless atomic is true. atomic is allowed only when every op is save_entry or delete_entry, and then they share one entry transaction. A save_entry input may set ref and relations: [{ field, ref }]. relations are applied only when atomic is true, after ids exist. Each sequential item returns success or the error, plus revisionId when it saved. A failure does not roll back earlier sequential items. The MCP transport body limit still applies.
batch_operations · Group: design
Run up to 50 save_page, save_component, save_chrome, save_entry, save_localization, or delete_entry calls in order. Not one transaction unless atomic is true. atomic is allowed only when every op is save_entry or delete_entry, and then they share one entry transaction. A save_entry input may set ref and relations: [{ field, ref }]. relations are applied only when atomic is true, after ids exist. Each sequential item returns success or the error, plus revisionId when it saved. A failure does not roll back earlier sequential items. The MCP transport body limit still applies.
Inputs
| Field | Required | Notes |
|---|---|---|
websiteId | required | |
operations | required | |
atomic | optional | |
dryRun | optional |