Microsoft 365 MCP Server

list-calendar-event-instances

list-calendar-event-instances

Read-only

Retrieve all occurrences of a recurring Microsoft 365 calendar event within a date range, including exceptions and modified instances, excluding canceled ones.

Instructions

The occurrences of a recurring series, if the event is a series master. This property includes occurrences that are part of the recurrence pattern, and exceptions modified, but doesn't include occurrences canceled from the series. Navigation property. Read-only. Nullable.

💡 TIP: Expand a recurring event into individual instances within a date range. Requires startDateTime and endDateTime query parameters in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Use this to see all occurrences of a recurring event.

Input Schema

TableJSON Schema

Name	Required	Description
`top`	No	Page size (Graph $top). Start small (e.g. 5–15) so responses fit the model context; raise only if needed. Use $select to return fewer fields per item. For more rows, use @odata.nextLink from the response instead of a very large $top.
`skip`	No	Items to skip for pagination. Not supported with $search.
`count`	No	Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains().
`expand`	No	Navigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as a message body fails with "Parsing OData Select and Expand failed", and an unsupported value may be ignored rather than reported. Request ordinary fields with $select instead.
`filter`	No	OData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search.
`search`	No	KQL search query in one pair of double quotes; directory (users/groups) instead quotes each clause with no outer pair. Cannot combine with $filter.
`select`	No	Comma-separated fields to return, e.g. id,subject,from,receivedDateTime
`eventId`	Yes	Value for the 'eventId' path segment. Pass it under the name 'eventId', not as 'id'. Use the 'id' field of the event object as returned by Microsoft Graph.
`orderby`	No	Sort expression, e.g. receivedDateTime desc
`timezone`	No	IANA timezone name (e.g., "America/New_York", "Europe/London", "Asia/Tokyo") for calendar event times. If not specified, times are returned in UTC.
`skiptoken`	No	Next page: the @odata.nextLink from the previous response. Keep the other arguments the same.
`calendarId`	Yes	Value for the 'calendarId' path segment. Pass it under the name 'calendarId', not as 'id'. Use the 'id' field of the calendar object as returned by Microsoft Graph.
`endDateTime`	Yes	The end date and time of the time range, represented in ISO 8601 format. For example, 2019-11-08T20:00:00-08:00
`fetchAllPages`	No	Follow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search.
`startDateTime`	Yes	The start date and time of the time range, represented in ISO 8601 format. For example, 2019-11-08T19:00:00-08:00
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`excludeResponse`	No	Exclude the full response body and only return success or failure indication
`expandExtendedProperties`	No	When true, expands singleValueExtendedProperties on each event. Use this to retrieve custom extended properties (e.g., sync metadata) stored on calendar events.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.154.2Sep 17, 2026

addedInput schema / properties / expand / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / expand / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / expand / type
```
Removed value: -"array"
```

addedInput schema / properties / orderby / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / orderby / type
```
Removed value: -"string"
```

addedInput schema / properties / select / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / select / type
```
Removed value: -"string"
```
addedInput schema / properties / skip / minimum
```
Added value: +0
```

changedInput schema / properties / skip / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / top / minimum
```
Added value: +0
```

changedInput schema / properties / top / type

Previous value: -"number"New value: +"integer"

Changed1 schema field changedv0.154.0Sep 12, 2026

changedInput schema / properties / skiptoken / description

Previous value: -"Opaque cursor for the next page, taken from the previous response. Copy the $skiptoken value out of @odata.nextLink (or paste the whole nextLink URL — the token is extracted from it) and resend it with the SAME $filter/$select/$expand/$top as the first call. Use this to walk pages one at a time instead of fetchAllPages. Omit it for the first page."New value: +"Next page: the @odata.nextLink from the previous response. Keep the other arguments the same."

Changed2 schema fields changedv0.153.0Sep 12, 2026

changedInput schema / properties / search / description

Previous value: -"KQL search query — wrap value in double quotes. Cannot combine with $filter."New value: +"KQL search query in one pair of double quotes; directory (users/groups) instead quotes each clause with no outer pair. Cannot combine with $filter."

addedInput schema / properties / skiptoken

Added value: +{
+  "description": "Opaque cursor for the next page, taken from the previous response. Copy the $skiptoken value out of @odata.nextLink (or paste the whole nextLink URL — the token is extracted from it) and resend it with the SAME $filter/$select/$expand/$top as the first call. Use this to walk pages one at a time instead of fetchAllPages. Omit it for the first page.",
+  "type": "string"
+}

Addedv0.134.4Jul 28, 2026
Removedv0.131.2Jul 18, 2026
Addedv0.114.0May 28, 2026
Removedv0.112.2May 22, 2026
Addedv0.110.0May 18, 2026
Removedv0.108.0May 15, 2026
Addedv0.96.0May 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses that the tool is read-only, nullable, and navigation-property backed, and specifies which occurrences are included (recurrence pattern, modified exceptions) and excluded (canceled occurrences). These details go beyond the annotations' readOnly/non-destructive hints, so the agent understands exactly what data it will see.

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?

The description is structured with a definition paragraph and a tip, and the tip front-loads the practical usage. Some phrases such as 'Navigation property' are redundant, but overall each sentence adds useful context and it is not bloated.

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?

For a complex tool with an extensively documented schema, the description covers the core behavioral caveats (series master only, canceled occurrences excluded) and usage context. It does not describe response shape, but since no output schema exists and the tool returns a list of occurrences, this is acceptable.

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?

Because the input schema already documents all 18 parameters with full descriptions, the description adds only the reminder that startDateTime and endDateTime are required and the format example. This is a useful reinforcement but not new semantic information, so baseline 3 is appropriate.

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 names the exact operation—expanding a recurring event into individual instances within a date range—and clarifies it applies only to series masters. This differentiates it from sibling tools that list or retrieve single calendar events, even though no sibling is named.

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?

The tip explicitly tells when to use the tool: to see all occurrences of a recurring event within a date range, and identifies the two mandatory query parameters. It does not mention exclusions or compare against sibling tools, but the context is unambiguous.

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

Deploy Server

list-calendar-event-instances

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools