queue_operations
Run multiple Google Workspace operations in one call: sequentially with result chaining, or batch one operation across many resources in a single API request.
Instructions
RENAMED to bulk_operations, which does the same thing. This name still works and will be removed in a future release. Do many things in one call, two ways. mode:'queue' (default) runs different operations in sequence, chaining results with $N.field — works for every tool. mode:'batch' does ONE operation across many resources in a single Google request — far fewer round trips, but only where Google publishes a batch method.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | queue (default): N operations, N API calls, in order, with $N.field references between them. batch: ONE operation across many resources in a single API call — no $N references, because there is no 'between'. | |
| tool | No | batch only — the tool to call, e.g. 'manage_contacts'. | |
| No | batch only — the account to act as. | ||
| items | No | batch only — one entry per resource. A bare id string is enough when that is all that differs, e.g. ['people/c1', 'people/c2']; use objects when items carry more, e.g. [{name: 'Ada Lovelace', contactEmail: 'ada@example.com'}]. Anything shared by the WHOLE batch — labels to add, a field mask — goes at the top level of this call, not in here. | |
| detail | No | summary: one-line status per operation (default) | full: include complete output from each operation | |
| operation | No | batch only — the operation to apply to every item, e.g. 'delete'. Ask for one that cannot batch and the error names the ones that can. | |
| operations | No | Operations to execute sequentially |