Patch Entry
patch_entryPartially update a content entry by sending only the fields to change. Use for targeted edits without altering publish state; call publish_entry separately to mint a new version.
Instructions
Partially update a content entry (HTTP PATCH). Only include fields you want to change (e.g. relations, one field). Saves NEVER change the publish state — call publish_entry explicitly to mint a new version. Prefer this over update_entry when you are not replacing the entire entry.
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": {
"collection_slug": "<collection_slug>",
"uuid": "<uuid>",
"data": "<data>"
},
"name": "patch_entry"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Fields to merge; omit unchanged fields. Richtext values are markdown strings. Relation fields: on write send the related entry's UUID string or numeric id only; one-to-one = one value, one-to-many = array of UUIDs/ids. Do not pass the nested entry object from get_entry/list_entries. Media fields: asset UUID strings and/or numeric asset ids (array when multiple). | |
| uuid | Yes | The entry UUID | |
| locale | No | Locale code | |
| collection_slug | Yes | The collection slug |