Update and publish a message template
Updating a published template creates a new draft. Existing sends stay on the published version until the new draft is explicitly published.
Update message template <MESSAGE_TEMPLATE_ID> so the pickup reminder also
includes the closing time. Preserve its existing channel and purpose, add a
required closing_time string variable, and show the proposed changes before
creating the draft. Preview it with realistic values, let me review the exact
rendered copy, then ask separately before publishing it.
The agent uses get_message_template to understand the current version, confirms update_message_template, previews the new draft with preview_message_template, and confirms publish_message_template separately.
Sample response
Updated version published
Version 4 replaced version 3 only after its draft preview was approved.
- Template
- Pickup reminder tmpl_example_pickup
- Previous published version
- 3
- Published version
- 4
- Unpublished changes
- No
| Step | Result |
|---|---|
| Update | Draft version 4 created |
| Preview | Closing time rendered as 6:00 PM |
| Publish | Version 4 published after confirmation |
Approved copy: “Hi Ama, order WEB-1042 is ready at Osu. Please collect it before 6:00 PM.”
Illustrative values. The exact presentation depends on the MCP client.
If the draft is not published, new sends continue using the previous published version. The send tool refuses a template with unpublished changes so that reviewed and delivered copy cannot silently differ.