Skip to main content
Glama

update_slides_speaker_notes

Overwrite speaker notes on a slide: delete existing notes and insert new plain text. Use empty string to clear notes without adding.

Instructions

Replace the speaker notes on a slide (deletes existing, inserts new).

Fully overwrites the slide's speaker-notes pane — this is NOT an append. Existing notes are deleted first, then the new text is inserted. Pass an empty string to clear notes without adding any. To read current notes before overwriting, use get_slides_speaker_notes.

Requires OAuth scope: https://www.googleapis.com/auth/presentations (write).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
presentation_idYesGoogle Slides presentation ID (from the URL after `/d/`).
page_object_idYesObject ID of the target slide. Get it from `get_presentation.slides[].objectId`. Must reference an existing slide with a notes-page shape; if the slide has no notes shape (rare — some custom layouts), the call returns an error string rather than failing.
notesYesNew speaker notes text to insert. Plain text only (no rich formatting). Replaces ALL existing notes on this slide. Pass `""` to clear without adding.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully explains behavior: it deletes existing notes and inserts new ones, and mentions that an empty string clears notes. It discloses a failure mode (slide without notes shape returns an error string), providing full transparency.

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 two sentences, front-loaded with the main action, and every sentence adds value without redundancy. It is highly concise yet complete.

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 the tool's straightforward nature, an existing output schema, and no annotations, the description covers purpose, behavior, failure modes, and alternatives. It provides all necessary context for correct agent invocation.

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 input schema has 75% coverage with descriptions for three of four parameters. The description does not add extra parameter-level details beyond the overall behavior, so it meets but does not exceed the baseline for the given coverage.

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 states 'Replace the speaker notes on a slide' with a specific verb and resource. It distinguishes from appending by saying 'NOT an append' and references a sibling tool for reading, providing clear purpose differentiation.

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?

The description explicitly says when to use (to replace notes) and when not (if you need to read first, use get_slides_speaker_notes). It also states the OAuth scope required, giving complete usage guidance.

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