Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Edit a calendar event already sent

edit_calendar_event
Destructive

Correct a WhatsApp calendar event this number already sent.

name and start_at are always required, plus whatever else the event has: description, end_at, join_link, location, has_reminder with reminder_offset_sec, and extra_guests_allowed. This REPLACES the whole event: anything you leave out is removed from it, including its location, reminder and guest setting, so send again every detail you want to keep. The event keeps its place in the chat and the guests keep the answer they already gave.

Use an edit to fix a mistake (a typo, the description, a link). When the date, time or place change and the guests must accept again, do not edit: cancel the event with cancel_calendar_event and send a new one with send_calendar_event, because the old answer does not carry over to a new event. Neither an edit nor a cancel changes the entry a guest already added to their own calendar with the card's "Add to calendar" button. It stays on the old date, and adding again creates a second entry, which only the guest can delete.

Only a calendar event can be edited here. Using this tool on any other message answers invalid_request: message_not_editable.

Only a message sent THROUGH Turbo Notify can be edited. One typed on the phone itself belongs to the same number but cannot be edited here, and neither can a message received from someone else.

The 15-minute limit does not apply to a calendar event.

The edit is accepted at once and the outcome arrives as an event: message.edited when it worked, message.edit.failed when WhatsApp or the platform could not apply it. Read them with list_events.

The number first appears online and its unread messages in that conversation are marked as read, then the edit happens. Opening the conversation this way is automatic and uses no quota of its own.

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": {
      "message_id": "<message_id>",
      "name": "<name>",
      "start_at": "<start_at>"
    },
    "name": "edit_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe event's title, up to 200 characters.
end_atNoWhen the event ends. ISO 8601 with an offset, and later than `start_at`.
locationNoWhere the event takes place: a map pin with an optional name and address.
start_atYesWhen the event starts. ISO 8601 with an offset, for example `2026-09-10T14:00:00Z`. A time without an offset is rejected.
join_linkNoA link guests can open to join, for example a video call.
message_idYesMessage id (`msg_…`), as returned by a send or by `list_messages`.
descriptionNoDetails shown on the event, up to 2000 characters.
has_reminderNoSet to true to remind guests before the event. Off when left out.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main
reminder_offset_secNoHow many seconds before the event the reminder goes off, for example 600 for ten minutes. Only takes effect together with `has_reminder`.
extra_guests_allowedNoSet to true to let guests bring extra people. Off when left out.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations say destructive=true; the description explains exactly what is destroyed — the event is fully replaced, so any omitted field (location, reminder, guest setting) is removed. It adds side effects annotations cannot express: the 15-minute edit limit does not apply, the number goes online and unread messages are marked read, the edit is asynchronous with `message.edited`/`message.edit.failed` events readable via `list_events`, and guest calendar entries are unaffected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core contract (replace-all) and the edit-vs-cancel routing, then layers edge cases in short paragraphs. It is long, but each paragraph carries distinct operational information; only the final paragraph about automatic conversation opening is marginally less essential.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers everything needed for an 11-parameter destructive mutation: replace semantics, error case (`invalid_request: message_not_editable`), eligibility rules, async outcome events and guest-visibility consequences. An output schema exists, and the description still usefully names the emitted events.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description adds real meaning beyond it: `name` and `start_at` are always required and the enumerated optional fields define a replace-all contract, so omitting a field clears it rather than leaving it unchanged — a default-semantics fact the schema's `default: null` does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Correct a WhatsApp calendar event this number already sent') and scopes it to messages sent through this number. It is immediately distinguishable from send_calendar_event and edit_text_message.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('fix a mistake: a typo, the description, a link') and explicit when-not, naming the exact alternative workflow: if date, time or place change, use `cancel_calendar_event` plus `send_calendar_event` instead. It also excludes non-calendar messages and phone-typed or received messages.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.