Skip to main content
Glama

get_slides_speaker_notes

Retrieve speaker notes from a slide in Google Slides. Use for auditing notes or reviewing content per slide.

Instructions

Read the speaker notes text from a single slide.

Returns the plain-text contents of the slide's speaker-notes pane (the area shown to the presenter in Presenter View, hidden from the audience). Useful for auditing/exporting notes, reviewing coverage per slide, or piping into transcripts. To modify notes, use update_slides_speaker_notes.

Requires OAuth scope: https://www.googleapis.com/auth/presentations.readonly (or broader). Read-only — safe to call repeatedly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
presentation_idYesGoogle Slides presentation ID (from the URL after `/d/`).
page_object_idNoObject ID of the target slide. Either this OR `slide_index` is required. Get it from `get_presentation.slides[].objectId`. Preferred over `slide_index` because object IDs are stable across slide reordering.
slide_indexNo0-based position of the slide in the deck. Used only if `page_object_id` is not provided. Index 0 = first slide.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It declares read-only nature, safe for repeated calls, and required scope. It does not specify error behavior (e.g., missing notes) or rate limits, but covers key behavioral traits.

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?

Four sentences, each serving a purpose: action statement, output description, use case and alternative, authority and safety. No redundancy, front-loaded with key information.

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?

Covers purpose, usage, authority, and safety. Assumes output schema exists (not shown) so return details are adequately described as plain-text. Missing edge-case handling but sufficient for typical use.

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 coverage is 75% (3 of 4 params have descriptions). The description adds context that the tool works on a single slide but does not elaborate on parameters beyond what schema provides. Baseline 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?

Clearly states it reads speaker notes from a single slide, specifies the return type (plain-text), and distinguishes from sibling tool update_slides_speaker_notes. Use cases for auditing/exporting are mentioned.

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?

Explicitly tells when to use (auditing/exporting notes) and when not (for modifications, use update_slides_speaker_notes). Also lists required OAuth scope and confirms it's safe to call repeatedly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server