Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_read

Read-only

Read a presentation to extract each slide's text by placeholder, tables, image counts, and speaker notes for review or content analysis.

Instructions

Read a presentation: every slide's text (by placeholder), tables, image count, and speaker notes.

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>"
    },
    "name": "slides_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
presentationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.8/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 earns credit by detailing what is actually returned – text per placeholder, tables, image count, notes – which is meaningful behavioral context given there is no output schema.

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 zero filler, listing the returned content in a scannable order. Nothing repeats the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read with no output schema, the description covers the return content well enough to set expectations. Minor gaps remain: whether image count is a summary versus image data, and whether notes are always included.

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?

The single parameter presentationId is self-describing and required, so an agent can reasonably infer intent. However, schema description coverage is 0% and the description says nothing about the parameter or where a valid ID comes from, so it adds no meaning beyond the schema.

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 (read) and resource (a presentation) and enumerates the exact content surfaced: slide text by placeholder, tables, image count, speaker notes. This clearly separates it from write-side siblings like slides_set_text or slides_add_image, though it never names a read alternative such as slides_get_thumbnail or docs_read.

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?

Usage is only implied: the description makes clear this is the tool for reading slide content, but it gives no explicit when-to-use or when-not-to-use guidance and never points to a sibling for cases like thumbnail rendering or raw file text.

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