Quick Add or Create Event: Which Calendar Tool Should an Agent Use?

Use quick_add_event for a low-stakes personal entry when you can inspect the result immediately. Use create_event when the date, time zone, attendees, reminders, or recurrence must be specified before the write. Both tools create an event; neither is a preview button.

The difference is in the request, not the prose

Google's Events: quickAdd reference describes creation from a simple text string. CalendarMCP's quick_add_event passes your text to that API and returns the created event. Its other input is an optional calendarId. There is no separate start, end, attendee list, reminder, or recurrence field in this tool. For example, Lunch with Sam November 10 at noonis an instruction to Google's parser, not a guarantee that the resulting time matches your intent.

CalendarMCP's create_eventinstead calls Google's Events: insert method with a required title and explicit start and end objects. It also accepts attendee emails, reminders, recurrence rules, and other fields. An explicit payload makes the intended time reviewable before an agent writes it. Google still determines whether the request succeeds; this is not a promise of delivery.

A concrete choice for a November meeting

Suppose you need a half-hour personal block on November 10, 2026 at noon in Los Angeles. The following is an illustrative create_eventinput, not the result of a live calendar test. The explicit offset is -08:00 on that date, and the named time zone is America/Los_Angeles.

{
  "calendarId": "your-calendar-id",
  "summary": "Lunch with Sam",
  "start": { "dateTime": "2026-11-10T12:00:00-08:00", "timeZone": "America/Los_Angeles" },
  "end": { "dateTime": "2026-11-10T12:30:00-08:00", "timeZone": "America/Los_Angeles" }
}

If you do not know the duration or calendar, ask before creating anything. Neither a friendly prompt nor a successfully parsed title establishes the intended end time. A vague phrase such as "next Tuesday afternoon" should not become an attendee-facing meeting without a person confirming the actual interval.

Read back the calendar you actually changed

1. Specify a writable calendarId when several calendars are connected. In the current CalendarMCP implementation, omitting it selects the first enabled calendar with write permission, which may not be the one you meant.
2. After the create response, compare its event ID, title, start, end, and calendar with the requested values. For a natural-language quick add, treat that comparison as mandatory.
3. Use get_event with that ID and calendar, or list_events for a narrow time window, to confirm what is now present. If the write times out without a response, check before retrying: the event may already exist.

This choice is based on the current tool implementations and Google's API references, not on a measured quick-add parsing success rate. The timeout recovery guide covers uncertain write outcomes. To connect a client or inspect tool inputs, the live homepage links to the setup and API docs.