Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_get_thumbnail

Read-only

Retrieve a PNG thumbnail URL for any slide to visually verify its content, layout, or design before sharing or presenting.

Instructions

Get a PNG thumbnail URL of a slide (to visually check it).

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": {
      "presentationId": "<presentationId>",
      "slide": "<slide>"
    },
    "name": "slides_get_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoMEDIUM
slideYesSlide objectId, or 1-based slide number
presentationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds the non-obvious fact that the return is a URL to a PNG rather than the image bytes, which affects how an agent must handle the result. It omits whether the URL is temporary, what resolution each size yields, or behavior on an invalid slide reference.

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?

A single front-loaded sentence with the resource and the return type stated immediately and no wasted wording. The parenthetical adds a real hint rather than filler.

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?

For a three-parameter read tool with no output schema, the description should say more about the returned URL (lifetime, how to use it) and about the size parameter's tradeoffs. The safety profile is covered by annotations, but the low schema coverage leaves real gaps the description does not fill.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — the 'slide' parameter is documented in the schema, but 'presentationId' and 'size' are not, and the description adds no meaning to any of them. It does not explain how size affects the thumbnail or clarify the objectId-vs-1-based-index ambiguity beyond what the schema already states.

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?

The description pairs a specific verb ('Get') with a specific resource ('PNG thumbnail URL of a slide'), so an agent knows exactly what comes back. It is clearly distinct from text-reading siblings like slides_read, though it does not name any sibling explicitly.

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 parenthetical '(to visually check it)' implies the use case — visual verification rather than content extraction — but there is no explicit guidance on when to prefer this over slides_read or when it is unnecessary. Usage must be inferred from the purpose statement.

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