Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_set_notes

Set or update speaker notes for a specific Google Slides slide by presentation ID and slide ID or 1-based number, so presenters can add talking points and context.

Instructions

Set the speaker notes of a slide.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond the annotations, such as whether existing notes are overwritten, what permissions are required, or how failures are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. Its brevity is appropriate structurally, though the minimal content leaves important details unstated.

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

Completeness2/5

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

For a mutation tool with three required parameters, no output schema, and low schema description coverage, the description is too sparse. It does not explain 'presentationId' or 'notes', nor does it describe the overwrite behavior an agent needs before invoking a speaker-notes update.

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%; only the 'slide' parameter is documented in the schema. The description implies that 'notes' holds speaker notes and 'presentationId' identifies a presentation, but it does not explain formats, overwrite semantics, or the distinction between slide objectId and 1-based slide number 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 states a specific verb and resource: 'Set the speaker notes of a slide.' This clearly distinguishes the operation from sibling tools such as slides_set_text. However, it offers no explicit differentiation from other slide-editing siblings beyond the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It only implies that it should be used when speaker notes need to be set.

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