grr

Overview Schema Source Related Servers Discussions Admin

slides.presentations.pages.getThumbnail

Generates a thumbnail URL for the latest version of a specified presentation page, with optional image size and PNG format.

Instructions

Generates a thumbnail of the latest version of the specified page in the presentation and returns a URL to the thumbnail image. This request counts as an expensive read request for quota purposes [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: get.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageObjectId`	Yes	[URL path segment] The object ID of the page whose thumbnail to retrieve.
`presentationId`	Yes	[URL path segment] The ID of the presentation to retrieve.
`thumbnailProperties.mimeType`	No	[query parameter] The optional mime type of the thumbnail image. If you don't specify the mime type, the mime type defaults to PNG. Values: `PNG` = The default mime type..
`thumbnailProperties.thumbnailSize`	No	[query parameter] The optional thumbnail image size. If you don't specify the size, the server chooses a default size of the image. Values: `THUMBNAIL_SIZE_UNSPECIFIED` = The default thumbnail image size. The unspecified thumbnail size implies that the server chooses the size of the image in a way that might vary in the future.; `LARGE` = The thumbnail image width of 1600px.; `MEDIUM` = The thumbnail image width of 800px.; `SMALL` = The thumbnail image width of 200px.; `WIDTH2000_PX` = The thumbnail image width of 2000px..

Output Schema

Name	Required	Description	Default
`width`	No
`height`	No
`contentUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 26, 2026

changedInput schema / properties / pageObjectId / description

Previous value: -"The object ID of the page whose thumbnail to retrieve."New value: +"[URL path segment] The object ID of the page whose thumbnail to retrieve."

changedInput schema / properties / presentationId / description

Previous value: -"The ID of the presentation to retrieve."New value: +"[URL path segment] The ID of the presentation to retrieve."

changedInput schema / properties / thumbnailProperties.mimeType / description

Previous value: -"The optional mime type of the thumbnail image. If you don't specify the mime type, the mime type defaults to PNG."New value: +"[query parameter] The optional mime type of the thumbnail image. If you don't specify the mime type, the mime type defaults to PNG. Values: `PNG` = The default mime type.."

changedInput schema / properties / thumbnailProperties.thumbnailSize / description

Previous value: -"The optional thumbnail image size. If you don't specify the size, the server chooses a default size of the image."New value: +"[query parameter] The optional thumbnail image size. If you don't specify the size, the server chooses a default size of the image. Values: `THUMBNAIL_SIZE_UNSPECIFIED` = The default thumbnail image size. The unspecified thumbnail size implies that the server chooses the size of the image in a way that might vary in the future.; `LARGE` = The thumbnail image width of 1600px.; `MEDIUM` = The thumbnail image width of 800px.; `SMALL` = The thumbnail image width of 200px.; `WIDTH2000_PX` = The thumbnail image width of 2000px.."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "contentUrl": {
+      "type": "string"
+    },
+    "height": {
+      "type": "integer"
+    },
+    "width": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses important traits: it is an HTTP GET, counts as an expensive read request for quota purposes, and returns a URL to the thumbnail image. It does not mention authentication scope or URL expiration, but the core behavioral profile is clear.

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 description is front-loaded with the core purpose and quota note, but it includes boilerplate about request bodies and typed parameters that is irrelevant for a GET operation. The sibling note is terse but adds some noise.

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?

An output schema exists and the input schema is fully described, so the description does not need to explain return values. It provides the essential context: the tool's purpose, quota cost, HTTP method, and sibling alternative. It could be slightly more complete by clarifying authentication or URL lifetime, but it is sufficient.

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 schema already documents all parameters thoroughly. The description adds only generic request-building notes and does not explain the meaning of parameters beyond what the schema provides.

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 states a specific verb and resource: generates a thumbnail of the latest version of a specified page and returns a URL to the image. It also names the sibling tool over the same resource ('get'), allowing an agent to distinguish thumbnail generation from full page retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names the alternative sibling ('get') but does not explicitly state when to use this tool versus that one. It implies usage by saying the tool returns a thumbnail URL, but lacks clear conditions or exclusions.

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

Deploy Server