Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Get Page Thumbnail

get_page_thumbnail

Read-onlyIdempotent

Generate a thumbnail URL for a specific slide in a Google Slides presentation to preview its content, with optional inline PNG output for clients that cannot fetch URLs.

Instructions

Generate a thumbnail URL for a specific page (slide) in a presentation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`inline`	No	Also return the rendered PNG itself as image content, so a multimodal client can look at the slide without fetching the URL. The URL is a short-lived googleusercontent link that sandboxed or egress-restricted clients often cannot reach. If the image cannot be fetched, the URL-only result is returned with a note saying so. Defaults to False.
`page_object_id`	Yes	The object ID of the page/slide.
`thumbnail_size`	No	Size of thumbnail ("LARGE", "MEDIUM", "SMALL"). Defaults to "MEDIUM".	MEDIUM
`presentation_id`	Yes	The ID of the presentation.
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.30.1Oct 3, 2026

addedInput schema / properties / inline

Added value: +{
+  "default": false,
+  "description": "Also return the rendered PNG itself as image content, so\na multimodal client can look at the slide without fetching the URL.\nThe URL is a short-lived googleusercontent link that sandboxed or\negress-restricted clients often cannot reach. If the image cannot\nbe fetched, the URL-only result is returned with a note saying so.\nDefaults to False.",
+  "type": "boolean"
+}

Addedv1.0.1Jul 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds nothing beyond that – it omits that the URL is a short-lived googleusercontent link and that the inline option can return the PNG, both of which live only in the schema. Adequate but thin given annotations carry most of the load.

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?

A single front-loaded sentence with no filler, stating verb, resource and scope immediately. It is efficient, though arguably too terse to carry usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and annotations cover the safety profile. However, the description omits any routing guidance among the many presentation/page siblings and does not mention the inline/short-lived-URL caveat that affects client behavior, leaving it only minimally complete.

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 all five parameters (including the nuanced inline and thumbnail_size behaviors) are documented in the schema itself. The description adds no parameter-level meaning beyond what the schema provides, so the 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 (generate) and resource (thumbnail URL for a page/slide in a presentation), which is clear and distinct from siblings like get_page or get_presentation. It does not explicitly name or differentiate against those siblings, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives (e.g., get_page for content vs. this for a visual), and no prerequisites such as required auth. Usage is only inferable from the purpose.

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

Deploy Server