Skip to main content
Glama
adamzaidi

icloud-mcp

by adamzaidi

create_event

Add new events to iCloud calendars with details like title, time, location, and recurrence rules. Supports both timed and all-day events across multiple calendars.

Instructions

Create a new event in an iCloud calendar. For all-day events use allDay:true and YYYY-MM-DD for start/end.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdYesCalendar ID to add the event to
summaryYesEvent title
startYesStart date/time — ISO 8601 (e.g. 2026-03-15T10:00:00) or YYYY-MM-DD for all-day
endNoEnd date/time — ISO 8601 or YYYY-MM-DD. Defaults to 1 hour after start.
timezoneNoIANA timezone (e.g. America/New_York). Use "UTC" or omit for UTC.
allDayNoTrue for all-day event (uses DATE values, no time)
descriptionNoEvent description / notes
locationNoEvent location
recurrenceNoiCal RRULE string (e.g. FREQ=WEEKLY;BYDAY=MO,WE,FR)
statusNoEvent status: CONFIRMED, TENTATIVE, or CANCELLED
reminderNoAlert this many minutes before the event (default 30, set to 0 to disable)

Implementation Reference

  • The `createEvent` function sends a PUT request to the CalDAV server to create a new event. It uses `serializeVEvent` to format the calendar data.
    export async function createEvent(calendarId, fields) {
      const { dataHost, calendarsPath } = await discover();
      const { ical, uid } = serializeVEvent(fields);
      const eventId = uid;
      const url = `${dataHost}${calendarsPath}${calendarId}/${eventId}.ics`;
    
      const resp = await davRequest('PUT', url, {
        contentType: 'text/calendar; charset=utf-8',
        body: ical,
      });
    
      if (resp.status !== 201 && resp.status !== 204 && resp.status !== 200) {
        throw new Error(`CalDAV PUT failed: ${resp.status} — ${resp.body.slice(0, 200)}`);
      }
    
      return { created: true, eventId, calendarId, etag: resp.etag };
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the iCloud domain and all-day event behavior, but omits safety details (idempotency, validation errors), authorization requirements, and what the tool returns upon success.

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?

Two sentences with zero waste: first establishes purpose, second delivers critical implementation detail for all-day events. Appropriately front-loaded and dense with actionable information.

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

Completeness3/5

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

For an 11-parameter creation tool with no output schema or annotations, the description covers the essential use case but leaves gaps regarding return values, error conditions, timezone handling behavior, and integration with list_calendars.

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?

Despite 100% schema description coverage, the description adds value by explicitly linking the allDay flag to the YYYY-MM-DD format requirement ('use allDay:true and YYYY-MM-DD'), reinforcing the parameter interaction imperatively.

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 the specific action ('Create a new event') and target resource ('iCloud calendar'), distinguishing it from sibling tools like update_event, delete_event, and email-related functions.

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

Usage Guidelines3/5

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

Provides specific syntax guidance for all-day events ('use allDay:true and YYYY-MM-DD'), but lacks broader guidance on when to use this versus suggest_event_from_email or prerequisites like obtaining calendarId from list_calendars.

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/adamzaidi/icloud-mcp'

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