Microsoft 365 MCP Server

list-specific-calendar-events

list-specific-calendar-events

Read-only

List events from one of the signed-in user's calendars, addressed by calendar ID.

Instructions

List events from one of the signed-in user's calendars, addressed by calendar ID.

💡 TIP: WARNING: Does NOT expand recurring events — only returns seriesMaster. Use get-specific-calendar-view instead.

Input 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(). The response then includes @odata.count, the total for the filtered collection, which can exceed the items returned when fetchAllPages hits its page/item cap.
`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". Request ordinary fields with $select instead. Some APIs accept only one relationship per request, so prefer a single value. Some relationships support nested selection, e.g. children($select=id,name).
`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
`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.
`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.
`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.

Changed2 schema fields changedv0.166.0Oct 14, 2026

changedInput schema / properties / count / description

Previous value: -"Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains()."New value: +"Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains(). The response then includes @odata.count, the total for the filtered collection, which can exceed the items returned when fetchAllPages hits its page/item cap."

changedInput schema / properties / expand / description

Previous value: -"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."New value: +"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\". Request ordinary fields with $select instead. Some APIs accept only one relationship per request, so prefer a single value. Some relationships support nested selection, e.g. children($select=id,name)."

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

Changed17 schema fields changedv0.96.0May 4, 2026

changedInput schema / properties / count / description

Previous value: -"Include count of items"New value: +"Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains()."

addedInput schema / properties / expandExtendedProperties

Added value: +{
+  "description": "When true, expands singleValueExtendedProperties on each event. Use this to retrieve custom extended properties (e.g., sync metadata) stored on calendar events.",
+  "type": "boolean"
+}

changedInput schema / properties / fetchAllPages / description

Previous value: -"Automatically fetch all pages of results"New value: +"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."

changedInput schema / properties / filter / description

Previous value: -"Filter items by property values"New value: +"OData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search."

changedInput schema / properties / orderby / description

Previous value: -"Order items by property values"New value: +"Sort expression, e.g. receivedDateTime desc"

removedInput schema / properties / orderby / items
```
Removed value: -{
-  "type": "string"
-}
```
changedInput schema / properties / orderby / type
```
Previous value: -"array"New value: +"string"
```

changedInput schema / properties / search / description

Previous value: -"Search items by search phrases"New value: +"KQL search query — wrap value in double quotes. Cannot combine with $filter."

changedInput schema / properties / select / description

Previous value: -"Select properties to be returned"New value: +"Comma-separated fields to return, e.g. id,subject,from,receivedDateTime"

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

changedInput schema / properties / select / type

Previous value: -"array"New value: +"string"

changedInput schema / properties / skip / description

Previous value: -"Skip the first n items"New value: +"Items to skip for pagination. Not supported with $search."

removedInput schema / properties / skip / minimum
```
Removed value: -0
```

changedInput schema / properties / skip / type

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

changedInput schema / properties / top / description

Previous value: -"Show only the first n items"New value: +"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."

removedInput schema / properties / top / minimum
```
Removed value: -0
```

changedInput schema / properties / top / type

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

First observedv0.31.0Jan 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond the annotations: recurring events are NOT expanded and only seriesMaster is returned. It does not mention throttling or payload-size caveats, but the critical gotcha is disclosed.

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?

Two short sentences, front-loaded with the tool's scope before the caveat. The '💡 TIP: WARNING:' prefix mixes two signals awkwardly, but there is no filler and every clause earns its place.

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 15-parameter, no-output-schema tool, the schema and annotations do the heavy lifting while the description supplies the one behavioral trap an agent must know (no recurrence expansion). Reasonably complete, though it could note pagination expectations without contradicting the rich schema.

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% across all 15 parameters, so the schema carries the full parameter burden (pagination, $filter/$search, $top guidance, fetchAllPages caps). The description only echoes the required calendar ID, adding no semantics beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List events') and scopes it precisely to 'one of the signed-in user's calendars, addressed by calendar ID'. This scope wording implicitly distinguishes it from list-calendar-events (all calendars), though it never names that sibling, keeping it short of 5.

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 warning gives an explicit when-not case (recurring event expansion) and names the correct alternative (get-specific-calendar-view). It stops short of 5 because it offers no guidance for the ordinary case versus list-calendar-events or get-calendar-view.

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

Deploy Server

list-specific-calendar-events

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools