Microsoft 365 MCP Server

list-drive-item-thumbnails

list-drive-item-thumbnails

Read-only

Collection of thumbnailSet objects associated with the item. For more information, see getting thumbnails. Read-only. Nullable.

Instructions

Collection of thumbnailSet objects associated with the item. For more information, see getting thumbnails. Read-only. Nullable.

💡 TIP: Lists thumbnail sets for a file. Each set contains small (96px), medium (176px), large (800px) thumbnails with url and dimensions. Returns empty for unsupported types (text docs). Use $select=small,medium,large or $expand=small($select=url) to fetch specific sizes. The returned URLs are short-lived — fetch the bytes immediately.

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
`driveId`	Yes	Value for the 'driveId' path segment. Pass it under the name 'driveId', not as 'id'. Use the 'id' field of the drive object as returned by Microsoft Graph.
`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.
`driveItemId`	Yes	Value for the 'driveItemId' path segment. Pass it under the name 'driveItemId', not as 'id'. Use the 'id' field of the drive item 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.

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
Addedv0.96.0May 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only (readOnlyHint=true, destructiveHint=false), but the description adds genuinely useful behavior beyond them: empty results for unsupported item types and the critical warning that returned URLs are short-lived and bytes must be fetched immediately. That is real operational context an agent cannot infer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The TIP block is dense and front-loaded with the information that matters, but the leading sentence duplicates Graph documentation prose and 'Read-only. Nullable.' merely restate what annotations and schema already convey. Roughly a third of the text does not earn 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 14-parameter read tool with no output schema, the description covers the return shape at a useful level (each set contains small/medium/large thumbnails with url and dimensions) plus the empty-result case and URL lifetime. Missing only how the shared pagination/query params interact with thumbnails specifically.

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?

Schema description coverage is 100%, so baseline is 3; the description earns above it by grounding generic $select/$expand parameters in thumbnail-specific values (small,medium,large and nested small($select=url)). It stops short of explaining pagination or top/skip in thumbnail terms, but adds meaningful specificity.

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?

The TIP sentence 'Lists thumbnail sets for a file' gives a specific verb and resource, and the size/url detail distinguishes it from generic drive-item retrieval siblings. The opening sentence is lifted doc prose ('Collection of thumbnailSet objects associated with the item'), which is weaker, but the tool's identity is unambiguous.

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?

It states a clear when-not: 'Returns empty for unsupported types (text docs)', and tells the agent to use $select/$expand for specific sizes. It does not name a competing sibling (e.g. get-drive-item or download-bytes) explicitly, so routing is inferred rather than spelled out.

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

Deploy Server

list-drive-item-thumbnails

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools