Push edits to draft
push_boardApply file changes to your open editing draft: text, exact edits, delete, rename, or a declared large binary. Deletes and replacements change the current draft; earlier checkpoints stay restorable. If a change needs edits you cannot state exactly, give a change plan instead. Retry with the same operationId. If upload links come back, PUT each within 5 min, then repeat the same call, which renews expired links. Never show them.
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": {
"board": "<board>",
"operationId": "<operationId>",
"expectedCheckpointId": "<expectedCheckpointId>",
"changes": "<changes>"
},
"name": "push_board"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| board | Yes | Your board: handle/slug or a boardrepo.com URL. | |
| changes | Yes | File changes against the current checkpoint, one entry per file. Combine renameTo with content, edits or upload in the same entry. | |
| operationId | Yes | Client-generated UUID. Reuse for retries of the same logical step; use a new one for a new edit or save. | |
| expectedCheckpointId | Yes | checkpoint.id from get_current_work. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||