Skip to main content
Glama
Sign In
Google Workspace MCP VE

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_page_thumbnail

Generate a PNG thumbnail URL for a slide, enabling quick visual previews without fetching the full image bytes.

Instructions

Generate a PNG thumbnail URL for one slide.

Useful for visual previews. Returns a Google-hosted URL (not the image bytes). The URL is short-lived — fetch and cache quickly. For slide element details use get_page. Requires the presentations.readonly OAuth scope.

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": "get_page_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
presentation_idYesParent presentation ID.
page_object_idYesSlide objectId from get_presentation.
thumbnail_sizeNo"LARGE" (~1600px wide), "MEDIUM" (~800px, default), or "SMALL" (~200px).MEDIUM

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.0
    • changedInput schema / properties / page_object_id / description
      Previous value: -"The object ID of the page/slide."New value: +"Slide objectId from get_presentation."
    • changedInput schema / properties / presentation_id / description
      Previous value: -"The ID of the presentation."New value: +"Parent presentation ID."
    • changedInput schema / properties / thumbnail_size / description
      Previous value: -"Size of thumbnail (\"LARGE\", \"MEDIUM\", \"SMALL\"). Defaults to \"MEDIUM\"."New value: +"\"LARGE\" (~1600px wide), \"MEDIUM\" (~800px, default),\nor \"SMALL\" (~200px)."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.5/5.0
Behavior4/5

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It reveals that the tool is read-only (requires presentations.readonly scope), returns a URL not image bytes, and that the URL is short-lived. No contradictions.

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?

Three concise sentences. First sentence states purpose, second gives usage guidance and return type, third explains URL behavior and scope. No wasted words, front-loaded.

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?

Given no output schema in the input, the description effectively explains what is returned (a Google-hosted URL) and its ephemeral nature. It also covers the OAuth scope and alternative tool. Complete for the tool's complexity.

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. The description adds no additional meaning beyond the schema for parameters. Baseline of 3 is appropriate.

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 explicitly states 'Generate a PNG thumbnail URL for one slide', which is a specific verb+resource combination. It distinguishes from sibling 'get_page' by noting 'For slide element details use get_page', making the purpose clear.

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?

Provides explicit guidance on when to use ('Useful for visual previews') and when not to ('For slide element details use get_page'). It also advises to fetch and cache quickly due to short-lived URLs, and mentions the required OAuth scope.

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