Change meal
update_mealChange a saved meal; only what you pass changes. Mark a planned meal as eaten with state logged (and eatenAt if the time differs) rather than creating it again; move, rename or annotate a meal the same way. A field left out keeps its value, and null clears name or notes. Items change one at a time by the item ids the meal returned: items.change sets a portion, items.remove drops items, and items.add adds foods as in create_meal; to swap a food, remove it and add the other. Ask one short question first if a food or portion is unclear. Pass photos the person attached as photos to add them; images replaces the saved photos, and a saved photo left out is deleted. Confirm the change only after success.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The id of the meal to change, as list_meals or create_meal returned it | |
| name | No | A new name for the meal; null clears it | |
| items | No | Changes to the meal's items, by the item ids the meal returned | |
| notes | No | New notes for the meal; null clears them | |
| state | No | logged for food eaten; planned only for a plan the person asked to save | |
| images | No | Photos already saved on this record to keep, or public https image links. New photos from the conversation go in photos, never here. | |
| photos | No | Photos the person attached in this conversation to keep with this record: pass the attachments themselves, never file paths | |
| eatenAt | No | When it was eaten, or for a plan when it will be, with its UTC offset | |
| timezone | No | The IANA timezone where the meal is eaten, such as America/New_York |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| day | Yes | ||
| name | Yes | ||
| items | Yes | ||
| notes | Yes | ||
| state | Yes | ||
| images | Yes | ||
| eatenAt | Yes | ||
| category | Yes | ||
| timezone | Yes | ||
| nutrition | Yes |