Skip to main content
Glama
Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

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

Render Page to Image

render_page_to_image
Read-onlyIdempotent

Render a slide or notes page as an image to inspect its layout and visuals without exporting the presentation to PPTX or PDF.

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.

This is the way to see a slide: use it instead of exporting the presentation to PPTX or PDF and rendering that.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_google_email": "<user_google_email>",
      "presentation_id": "<presentation_id>",
      "page_object_id": "<page_object_id>"
    },
    "name": "render_page_to_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoImage 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_idYesThe object ID of the page/slide to render.
presentation_idYesThe ID of the presentation.
user_google_emailYesThe user's Google email address. Required.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld behavior, so the safety profile is covered. The description adds useful non-annotation context by stating the output arrives as image content rather than a file path or text. It does not discuss cost or size trade-offs itself, but those are fully documented in the schema's size parameter, so the gap is minor.

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

Conciseness5/5

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

Two short sentences with zero filler: the first states the action and output, the second states the routing rule. The purpose is front-loaded before the alternative guidance, which is the right order for an agent scanning for fit.

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?

Annotations cover the safety profile, the input schema fully documents all four parameters, and an output schema exists so return values need no prose. The description still covers the two things structured data cannot express: what the tool is for and which alternative approach to avoid.

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's schema text is unusually thorough (pixel widths, readability guidance, token costs). The description adds no parameter-level detail beyond what the schema already supplies, so the baseline 3 applies.

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 gives a specific verb and resource ("Render a slide ... to an image") and widens the scope precisely ("any page, including notes pages") while stating the return form ("return it as image content"). It also gives the motivating intent ("for looking at a slide's layout and visuals"), so an agent knows exactly what this produces without opening the schema.

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?

It explicitly names the approach it replaces: "use it instead of exporting the presentation to PPTX or PDF and rendering that." That is a decisive when-to-use rule that selects this tool over an export-then-render path, leaving no real inference required.

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

Deploy Server

Other Tools