Microsoft 365 MCP Server

list-mail-folder-messages-delta

list-mail-folder-messages-delta

Read-only

Get only new, updated, or deleted messages in a mail folder via delta tokens. First call returns all messages and a delta link; subsequent calls with that link fetch just changes.

Instructions

Get a set of messages added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriately applying state tokens in one or more of these calls, you can query for incremental changes in the messages in that folder. It allows you to maintain and synchronize a local store of a user's messages without having to fetch the entire set of messages from the server every time.

💡 TIP: Incremental sync of messages within a mail folder. Graph only supports delta scoped to a folder — use mailFolder-id = 'inbox' for the well-known inbox, or another folder id from list-mail-folders. First call returns all messages plus @odata.deltaLink; subsequent calls with that link return only changes (created/updated/deleted). @odata.nextLink paginates within a single delta window. Deltas expire after ~30 days of inactivity — start over if the server returns 410. Prefer this over full re-list for polling.

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
`orderby`	No	Sort expression, e.g. receivedDateTime desc
`skiptoken`	No	Next page: the @odata.nextLink from the previous response. Keep the other arguments the same.
`changeType`	No	A custom query option to filter the delta response based on the type of change. Supported values are created, updated or deleted.
`mailFolderId`	Yes	Value for the 'mailFolderId' path segment. Pass it under the name 'mailFolderId', not as 'id'. Use the 'id' field of the mail folder 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

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.8/5.0

Behavior5/5

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

Annotations already mark it as read-only/non-destructive. The description adds behavioral details beyond annotations: delta links expire after ~30 days of inactivity, a 410 response means to start over, @odata.nextLink paginates within a window, and the first call returns all messages plus a deltaLink. This gives the agent operational expectations without contradicting the annotations.

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 longer than typical but well-structured: a formal paragraph explaining the delta concept, followed by a TIP block with operational details. No sentence is superfluous; all content is relevant to calling the tool correctly. It could be slightly trimmed, but the front-loaded intent and structured TIP keep it clear.

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?

Given the 14 parameters and no output schema, the description covers everything an agent needs: the delta token flow, pagination via nextLink, expiration handling, and practical folder selection. The schema already documents each parameter, so the only missing piece would be response format, but the description explains the key response fields (deltaLink, nextLink) and the tool's read-only nature. Complete for its purpose.

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?

The schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The description's TIP adds practical value by suggesting `mailFolderId = 'inbox'` as a well-known value and referencing list-mail-folders for discovering folder IDs, which goes beyond the schema's statement that the ID should come from a Graph object. This extra guidance earns a 4.

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 opens with a clear verb phrase 'Get a set of messages added, deleted, or updated in a specified folder' and explains the delta-increment concept. It distinguishes itself from a plain GET by specifying that it returns changes only when state tokens are applied, which differentiates it from siblings like list-mail-folder-messages.

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?

The TIP section explicitly says 'Prefer this over full re-list for polling,' naming the alternative behavior. It also states Graph only supports delta scoped to a folder, constraining when this tool is appropriate versus a folder-less delta or a full message list. First-call vs subsequent-call behavior is described, so the agent knows when to use it.

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

Deploy Server

list-mail-folder-messages-delta

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools