Skip to main content
Glama

create_event

Add an event to your iCloud Calendar, returning the new event's ID. Supports title, start, duration, location, recurrence, and participants.

Instructions

Create a calendar event. Returns the new event's id.

Use update_event to change an existing event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoEmail address to organize the event from when inviting participants. Must match one of the account's own addresses. If omitted, the account's primary address is used.
colorNoDisplay color, as a six-digit hex value (e.g. "#ff0000").
startYesStart date-time in ISO 8601 format (e.g. "2026-03-15T14:00:00").
titleYesEvent title.
durationNoDuration in ISO 8601 format, e.g. "PT1H" (1 hour) or "PT30M" (30 minutes). For an all-day event set isAllDay and give a whole-day duration like "P1D" or "P2D". Defaults to PT1H, or P1D when isAllDay.
isAllDayNoSet true for a true all-day (date-only) event such as a birthday, holiday, or multi-day trip. All-day events float: they have no time of day and no time zone, and never shift when viewed in another zone. Give 'start' as a date ("2026-07-03"; any time part is ignored) and 'duration' in whole days. (Note: a midnight start with duration P1D is NOT an all-day event -- it is a 24-hour timed block. Use this flag instead.)
locationNoLocation name or address.
timeZoneNoIANA time zone (e.g. "America/New_York"). Defaults to the server's zone. Ignored for all-day events, which have no time zone.
calendarIdNoCalendar to add the event to. Use list_calendars to find calendar IDs. Defaults to the user's first writable calendar.
recurrenceNoMake this a recurring event. Properties: frequency (required, one of "daily", "weekly", "monthly", "yearly"), interval (repeat every N, default 1), byDay (array of day codes for weekly: ["mo","tu","we","th","fr","sa","su"]), count (stop after N occurrences), until (stop after this date-time). Examples: {"frequency": "weekly"}; {"frequency": "weekly", "interval": 2, "byDay": ["mo","we","fr"]}.
descriptionNoEvent description or notes.
participantsNoInvitees, e.g. [{"name": "Jo", "email": "jo@example.com"}]. The account is added automatically as organizer; do not include it here. THIS SENDS REAL INVITATION EMAILS immediately, and they cannot be recalled -- omit this argument unless the user asked for guests.
Behavior2/5

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

With no annotations, the description carries the full burden, but it only mentions creating an event and returning an id. It omits important behavioral traits such as the permanence of creation, that non-default parameters like participants may send irreversible invitation emails, or any permission requirements.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the primary action, and includes only essential supplementary guidance. No filler or redundant information.

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

Completeness2/5

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

Despite a rich schema, the tool has 12 parameters and no annotations, and the description lacks critical context such as the participant email side effect, calendar selection default, or all-day event nuances. These details exist in the schema but are not surfaced in the description, making it insufficient for an agent to safely invoke the tool without deep parameter inspection.

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

Parameters3/5

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

Schema description coverage is 100%, with detailed parameter descriptions for all 12 fields, so the baseline is 3. The tool description itself adds no parameter-level meaning beyond what the schema already provides.

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?

The description clearly states 'Create a calendar event' with a specific verb and resource, and notes it returns the new event's id. This distinguishes it from sibling tools like list_calendars, search_events, and update_event, especially with the explicit pointer to update_event for modifications.

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?

It explicitly states when to use the tool (to create a new calendar event) and gives an alternative for a related operation: 'Use update_event to change an existing event.' This provides a clear when-not and alternative, covering the main ambiguity.

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/duanefields/calendar-mcp'

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