Skip to main content
Glama

Create an event

create_event

Create Google Calendar events with times, attendees, reminders, recurrence, and Google Meet; avoid conflicts by checking free/busy slots first.

Instructions

Creates an event and returns it (id, htmlLink, start/end, attendees, hangoutLink when add_meet). Times: EITHER start_date_time + end_date_time (RFC3339; add time_zone for recurring events) OR start_date + end_date for all-day (end_date is EXCLUSIVE — the day after the last day). recurrence makes it a recurring series. attendees invites guests — but the API sends invitation emails ONLY with send_updates=all (the default notifies nobody). add_meet attaches a Google Meet link (may come back status=pending — re-run get_event for the final URL). This is a plain calendar write: it does not check for conflicts — call query_free_busy first to find a free slot. Never blindly re-send after a timeout or 5xx: the event may already exist — check with list_events first, or you will create a duplicate and re-invite everyone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesEvent title.
add_meetNoAttach a Google Meet conference. The returned conferenceData may be status=pending — re-run get_event for the final Meet link.
color_idNoEvent color id ("1".."11"; the palette is fixed by Google).
end_dateNoAll-day event end date, EXCLUSIVE — the day after the last day (a one-day event on the 5th ends on the 6th).
locationNoFree-form location, e.g. a room name or address.
attendeesNoGuest list. On update this REPLACES the whole list — fetch the event first and send the complete new list. Invitation emails go out only with send_updates=all.
remindersNoCustom reminders (max 5). Setting this turns default reminders off for the event.
time_zoneNoIANA time zone for start/end (e.g. "Europe/Berlin"). REQUIRED for recurring events; otherwise optional when the RFC3339 offsets already say everything.
recurrenceNoRRULE/RDATE/EXRULE/EXDATE lines (RFC 5545) making the event recurring, e.g. ["RRULE:FREQ=WEEKLY;BYDAY=MO,WE"]. Requires the timed pair plus time_zone.
start_dateNoAll-day event start date (YYYY-MM-DD). Pair with end_date.
visibilityNoWho can see event details on a shared calendar.
calendar_idYesThe calendar id from list_calendars, or "primary" for the authenticated user's main calendar.
descriptionNoEvent description (plain text or simple HTML).
send_updatesNoWho receives an email about this change: all guests, only guests outside your organization, or nobody. Defaults to none — attendees are NOT notified unless you pass all.
transparencyNoopaque = the event blocks time in free/busy (default); transparent = it does not (shows as free).
end_date_timeNoTimed event end, RFC3339. Pair with start_date_time.
start_date_timeNoTimed event start, RFC3339 (e.g. 2026-09-01T10:00:00+02:00 or ...Z). Pair with end_date_time.
guests_can_modifyNoWhether guests may edit the event.
use_default_remindersNoUse the calendar's default reminders (ignored when reminders[] is given).
guests_can_invite_othersNoWhether guests may invite more people.
guests_can_see_other_guestsNoWhether guests can see the guest list.
Behavior5/5

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

Annotations already mark this as a non-read, non-idempotent write, and the description goes well beyond them: it discloses no conflict checking, the pending Meet link behavior, notification defaults, and duplicate-creation risk. These are critical behavioral traits the agent would otherwise only discover at runtime.

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?

Every sentence carries high-value information and there is no filler, but the description is a single dense paragraph that could be easier to scan with structured bullets. It is appropriately sized for a 21-parameter creation tool, just not optimally organized.

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?

Given the complexity, the absence of an output schema, and the minimal annotations, the description is exceptionally complete: it explains return values, time semantics, recurrence requirements, attendee notifications, the pending Meet state, conflict checking, and idempotency risks. An agent has enough to call it correctly and even to avoid common failures.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds essential semantic rules the schema does not convey: the EITHER/OR time-mode pairing, end_date exclusivity, time_zone being required for recurring events, recurrence requiring the timed pair, and send_updates defaulting to no notifications. This meaningfully exceeds the structured field descriptions.

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: 'Creates an event' and immediately lists what is returned. It distinguishes itself from siblings like update_event and get_event by making it a creation operation with a clear output contract.

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?

Provides explicit when-to-use guidance and alternatives: call query_free_busy first to find a free slot, and check list_events before re-sending after timeouts to avoid duplicates. It also warns about send_updates defaults, which directly affects whether invitations are sent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/A1-x-Tech/mcp-google-calendar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server