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

Render Page to Image

render_page_to_image

Read-onlyIdempotent

Renders a slide or any page, including notes pages, to image content for inspecting layout and visuals.

Instructions

Render a slide (or any page, including notes pages) to an image and return it as image content, for looking at a slide's layout and visuals.

Input Schema

Name	Required	Description	Default
`size`	No	Image width. One of "SMALL" (200px), "MEDIUM" (800px), "LARGE" (1600px) or "WIDTH2000_PX" (2000px). Defaults to "MEDIUM". Start at MEDIUM: it reads titles and body text. Use LARGE for small text such as tables, chart labels and footnotes. WIDTH2000_PX rarely reads more than LARGE. SMALL shows layout only; its text is unreadable. Token cost and the resolution the model sees depend on the model: Claude models with high-resolution vision read MEDIUM at ~460 image tokens, LARGE at ~1,850 and WIDTH2000_PX at ~2,900, while other models may downscale LARGE and WIDTH2000_PX and count tokens differently.	MEDIUM
`page_object_id`	Yes	The object ID of the page/slide to render.
`presentation_id`	Yes	The ID of the presentation.
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.2.0Oct 24, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds that the return is image content, which is useful, but nothing beyond that such as whether notes pages render differently or any pagination/size caveats (those live in the schema).

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 waste. It could be marginally sharper by naming the sibling it complements, but structure is clean.

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?

An output schema exists, so return values needn't be explained, and the operation is a simple read. However, an agent choosing between get_page and render_page_to_image still lacks explicit differentiation, leaving a small routing gap.

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% and the size parameter is documented in unusually rich detail in the schema itself. The description adds no parameter meaning, 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 (render) and resource (slide/page), plus the concrete side effect of returning image content. It does not explicitly differentiate from the closely named sibling get_page, so it lands just 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 Guidelines3/5

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

The phrase 'for looking at a slide's layout and visuals' implies the use case, but there is no explicit when-to-use-vs-get_page routing or exclusion guidance. Usage is inferred rather than stated.

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

Deploy Server