google-slides-mcp

render_page

Convert a Google Slides page into a PNG image to visually verify its rendering. Supports small, medium, and large size options.

Instructions

Render a slide to a PNG image for visual verification. (1 expensive call.)

Returns the server-side rendered pixels of the slide — the same image a viewer sees — so you can confirm output looks correct. Rendering is per-page by design (the thumbnail endpoint is an expensive quota operation).

Args: presentation_id: The presentation ID. page_id: The slide object ID. size: LARGE (~1600px), MEDIUM (~800px), or SMALL (~200px) wide.

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": {
      "presentation_id": "<presentation_id>",
      "page_id": "<page_id>"
    },
    "name": "render_page"
  }
}

Input Schema

Name	Required	Description	Default
`presentation_id`	Yes
`page_id`	Yes
`size`	No	LARGE, MEDIUM, or SMALL	MEDIUM

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the call is expensive and returns the same image a viewer sees, but does not detail side effects, auth requirements, or the exact nature of the returned data (e.g., format, base64 encoding). This is adequate but not exhaustive.

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?

The description is concise and front-loaded: the first sentence states the purpose. It uses two paragraphs plus an args list, with no wasted words. Every sentence provides value.

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?

The description does not have an output schema to rely on, so it should describe the return format. It mentions 'returns the server-side rendered pixels' but does not specify if it's a base64 PNG blob or binary data. With only 3 parameters and moderate complexity, more detail on the output would improve completeness.

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?

The description adds meaning beyond the schema: it explains 'presentation_id' as the presentation ID, 'page_id' as the slide object ID, and 'size' with illustrative pixel widths (LARGE ~1600px, etc.). The schema only provides a brief description for size, so the description significantly enhances understanding.

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 clearly states the verb 'render', resource 'a slide', and purpose 'for visual verification'. It distinguishes from siblings by explicitly noting it's per-page and that the thumbnail endpoint is expensive, which aligns with the tool's role.

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?

The description explains the tool is used to confirm output looks correct and mentions it's a per-page operation with a cost implication. It does not explicitly name alternatives or when not to use, but provides sufficient context for an agent to infer appropriate use.

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