Skip to main content
11 tools. Each one is also a REST route and a CLI command, from the same definition: the same input, the same output, the same errors.

get_calendar_event

Everything about one event. Guests, video link, location and description: what the list deliberately omits because it would be fetched for every event to show a few. meetLink prefers Google’s own conferencing data and falls back to a link found in the location or description, which is where a Zoom or Teams invitation usually is. canRsvp and canEdit say what this account may do, so the app does not offer a button Google will refuse.

Input

Output

Example

get_calendar_status

Whether Google Calendar is connected. configured means this deployment has a Google client, so connecting is possible. connected means the authorization has been completed. The refresh token is never returned.

Input

This tool takes no arguments.

Output

Example

list_calendar_events

Events in a window. Events from the chosen calendars between two instants, recurrences already expanded into their occurrences. Cancelled events are left out. Without calendarIds, only the primary calendar is read. At most 25 calendars per call. A calendar that refuses the read is skipped rather than failing the whole window: one calendar the account lost access to must not blank the day.

Input

Output

Example

list_calendars

The calendars this account can see. The account’s calendar list, primary first and then by name. Returns an empty list with connected: false rather than an error when Google is not connected: not being connected is a state the app draws, not a failure.

Input

This tool takes no arguments.

Output

Example

create_calendar_event

Create an event. Creates an event in the chosen calendar. allDay sends dates rather than instants, and the end is exclusive: a single all-day event ends the following day, which is how Google models it. meet asks Google to mint a real Meet link; the response carries it. Guests are emailed only when there are guests: notifying nobody still costs a round trip.

Input

Output

Example

delete_calendar_event

Delete an event. Removes the event from Google. This is not our archive: there is no undo, and the guests lose it too. An event already gone answers as a success, because the caller’s intent is satisfied.

Input

Output

Example

disconnect_calendar

Disconnect Google Calendar. Forgets the refresh token, so nothing further can be read. Reconnecting is one authorization away: there is nothing to re-enter.

Input

This tool takes no arguments.

Output

Example

move_calendar_event

Reschedule an event. Moves an event to new times: what dragging it in the calendar does. Guests are notified.

Input

Output

Example

rename_calendar_event

Rename an event. Changes the title. Guests are notified, because the title is what they see.

Input

Output

Example

rsvp_to_calendar_event

Answer an invitation. Sets your own attendance and tells the organiser. The event is read back first so only your own line changes: Google’s attendee list is patched whole, and sending a shortened one would drop every other guest.

Input

Output

Example

start_calendar_auth

Begin the Google authorization. Returns the URL to open. It carries a one-time state bound to your account, which the callback checks before accepting anything: without it, a callback would accept a code obtained by somebody else.

Input

This tool takes no arguments.

Output

Example