icloud-mcp

Overview Schema Source Related Servers Discussions Admin

Calendar List Events

calendar_list_events

Read-onlyIdempotent

Retrieve iCloud calendar events for a date range, optionally filtered by calendar, with recurring series expanded into individual occurrences.

Instructions

List events in a date range, sorted by start.

Each entry has id/url, summary, description, location, start, end (ISO 8601 with offset, or a date for all_day events), start_timezone, recurring, rrule, attendees and calendar. Recurring series are expanded into one entry per occurrence; all occurrences share the series id, so update/delete apply to the whole series.

Input Schema

TableJSON Schema

Name	Required	Description
`end_date`	No	Range end, inclusive for dates (YYYY-MM-DD or ISO datetime). Default: 365 days ahead.
`start_date`	No	Range start (YYYY-MM-DD or ISO datetime). Default: 90 days ago.
`calendar_id`	No	Calendar URL/ID from calendar_list_calendars. Omit to use all event calendars (or the first one when creating).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 27, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds critical context: recurring series are expanded into per-occurrence entries sharing a series id, with update/delete applying to the whole series. Also clarifies date formats for all-day events. This goes well beyond annotation hints.

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 concise paragraphs: the first front-loads the main action, the second details entry structure and recurring behavior. Every sentence earns its place, with no fluff.

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?

An output schema exists, parameters are fully documented, and the description covers edge cases (all-day event dates, recurring expansion, series ID semantics). An agent has everything needed to call this correctly.

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%, so the input schema already documents each parameter with defaults and formats. The description mentions 'date range' but adds no additional parameter-specific meaning. Baseline of 3 is appropriate when schema carries the detail.

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?

Clear verb and resource: 'List events in a date range, sorted by start.' It states exactly what the tool does and distinguishes it from search, creation, and other calendar operations. The scope (date range) is explicit.

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?

Provides clear context that this lists events in a range, distinguishing it from creation/update/delete. However, it does not explicitly contrast with calendar_search_events or state when to prefer one over the other. No explicit when-not-to-use guidance.

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