Update a resource record
update_resourceUpdate a record by ID, merging only specified fields to preserve untouched data. Use expected_updated_at to prevent overwriting concurrent changes, with conflict refusal and dry-run support.
Instructions
Update a record by id. Only the fields in body change; the server merges them over the current record (portal PUT is full-replace) so untouched fields are preserved. Same write gating as create_resource. For loop/parallel safety, pass expected_updated_at (the updated_at you saw when reading) — the write is then refused with a conflict if anyone changed the record in between, instead of silently overwriting their work.
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": {
"resource": "<resource>",
"id": "<id>",
"body": "<body>"
},
"name": "update_resource"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Record id to update. | |
| body | Yes | Fields to change. Unknown fields are dropped. | |
| dry_run | No | Run every gate and report the exact merged body that would be written, without writing. | |
| resource | Yes | Resource type. Call describe_resource for fields and supported verbs. | |
| expected_updated_at | No | Optimistic-concurrency token: the record's updated_at from your read. Refuses with a conflict if the live record has moved — re-read, re-apply, retry. |