Skip to main content
Glama

Create an event

events_create
DestructiveIdempotent

Create an event in one of a connected account's own calendars: the one named by the calendarId calendars_list gives, else the account's default; a calendar only shared with the account is refused. Guests are invited by that account's provider, Microsoft or Google, from its own address. A timed event's start and end are instants with their offset, the end no earlier than the start, so an entry of no length is taken; an all-day event's are dates, its end the day after its last. It is written in the person's own time zone, so an invitation shows that zone's time, and the answer gives its times in the zone it names under timeZone. A meeting with guests, no location and no video gets the person's default meeting link as its place. How it shows, its privacy, reminders, kind and video link are each refused with the reason where the account's provider lacks them. An Outlook subject takes at most 255 characters. repeat makes it a recurring series, each occurrence keeping the start's own hour in the person's time zone across clock changes. Who hears of it is notify's choice. Repeating a create whose answer was lost, with the same arguments, finds the event the first made rather than making a second - for the rest of that day (UTC), on Outlook only while Microsoft also recognises the repeat - so two events meant as two differ in some argument. Each guest's own times are answered under guestTimes in their time zone where it is known - the one guestZones names for them, else the one a member of the person's circles stored - and any other guest's zone as unknown, their time counted as the person's. A meeting any part of which falls, for a guest of known zone, outside 09:00-18:00 or on a Saturday or Sunday in that zone - an all-day one only on a Saturday or Sunday - is not sent: the refusal names each such guest and their time, and it goes out only once the call passes unusualHoursAgreed true on the person's word. A series is checked by its first occurrence; the person's own hours are never held.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYes
bodyNo
kindNoGoogle makes either only in a Workspace account's main calendar, timed; Outlook makes out of office alone, shown away.
startYes
videoNoA Meet link on a Google account or a Teams link on a work Microsoft account, given back under joinUrl.
guestsNoAddresses to invite.
notifyNoWho the provider tells: every guest where omitted, externalOnly only guests outside Google Calendar, none nobody. Outlook tells every guest of a meeting it makes, changes or cancels, so there only an answer goes untold.
repeatNoMakes it a recurring series, from its start, without end unless until or count is named.
showAsNoHow it shows; Google shows busy or free alone. Busy where omitted.
accountYesThe connected account, by the address calendars_list names.
privacyNoThe calendar's own where omitted.
subjectYes
locationNo
providerNoThe account's provider, as calendars_list names it; needed only where two connected accounts share an address.
remindersNoMinutes before its start each reminder sounds, Outlook keeping one; empty for none, the calendar's own where omitted.
calendarIdNoThe calendar to create it in, by the calendarId calendars_list names; the account's default where omitted.
guestZonesNoA guest's own time zone, only as the person names it - never inferred from an address, a language or a provider.
unusualHoursAgreedNoTrue only once the person has agreed to send at the hours an answer named as unusual for a guest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Far exceeds what annotations provide: the idempotency rule is spelled out precisely (same arguments find the event the first made rather than a second, for the rest of that day UTC, Outlook only while Microsoft recognises the repeat) which is far richer than idempotentHint=true. It also discloses which inputs are refused and why, the unusual-hours send block, and the default meeting-link behavior.

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

Conciseness3/5

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

Information density is high and the calendar rule is front-loaded, but the archaic, clause-heavy prose is hard to parse and there is no structure (no grouping of ids, guests, recurrence, sending). Much of the content earns its place given 18 parameters, but the packaging makes it harder than it needs to be.

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

Completeness4/5

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

With no output schema, the description does carry return-shape context (the answer's times in its timeZone, guestTimes, joinUrl) and covers invitation, notification, recurrence and refusal branches. It is close to complete for a tool this complex, though a few enum params (kind, showAs) get less prose than their provider caveats deserve.

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 description coverage is 72%, above baseline, yet the description still adds semantics the schema lacks: the Outlook 255-character subject cap, the instant-vs-date difference between start and end, and that each recurrence keeps the start's own hour across clock changes. These are genuine additions, not restatements.

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?

Opens with a specific verb+resource ('Create an event in one of a connected account's own calendars') and immediately scopes it: own calendars only, a shared-with calendar is refused. That scope cleanly separates it from events_edit, events_list and polls_create in the sibling set.

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

Usage Guidelines4/5

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

Gives concrete selection rules (which calendar via calendarId from calendars_list, else default), the refusal condition for shared calendars, the provider caveats, and the exact gate for unusualHoursAgreed. It never names an alternative sibling ('use events_edit to...'), so it stops short of a 5.

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.

Resources