Batch Update Entries
batch_update_entriesUpdate multiple existing journal entries in a single transaction, up to 50 per batch, to keep project memory changes consistent and atomic.
Instructions
Update multiple existing journal entries in a single transaction. Max 50 per batch. REQUIRED: You MUST include project_number. Extract this by querying memory://agent-id.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "batch_update_entries"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| updates | No | ||
| auto_index | No | ||
| workspace_id | No | Optional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key. | |
| project_number | No | Numeric project ID applied to batch updates when omitted per item. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Error code (e.g. VALIDATION_ERROR, INTERNAL_ERROR) | |
| count | No | ||
| error | No | Human-readable error message | |
| details | No | Additional error context | |
| success | No | ||
| updated | No | ||
| category | No | Error category (validation, query, connection, internal) | |
| notFound | No | ||
| suggestion | No | Suggested fix for the error | |
| recoverable | No | Whether the error is recoverable | |
| indexStatuses | No | ||
| aggregated_errors | No | Details of individual errors in a multi-step operation |