set_speaker_notes
Replaces a slide's speaker notes with the given text (empty string clears them). The tool resolves the slide's speakerNotesObjectId internally and rewrites that shape atomically — you pass the slide's object id, not the notes shape id. Notes are visible in the presenter view and exported by forma...
This record as markdown: /tools/a1-x-tech-mcp-google-slides/set-speaker-notes.md
What set_speaker_notes does on Mcp Google Slides
AI agents use set_speaker_notes to create or update resources in Mcp Google Slides, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Slides environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | The new speaker notes; empty string clears them. \n starts a new paragraph. |
presentation_id | string | Yes | The presentation id — the long id from the URL (docs.google.com/presentation/d/<presentationId>/edit) or from create_presentation output. |
slide_object_id | string | Yes | The slide's object id (from list_slides) — not the notes page id. |
Parameters from the server's own tool schema.
Why set_speaker_notes is rated Medium
Modifies presentation metadata reversibly without destructive or irreversible effects on core content.
From the tool's definition Replaces a slide's speaker notes with the given text.
Attacks that exploit this kind of access
The rule that runs set_speaker_notes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Slides, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_speaker_notes, this is the rule to start with:
set_speaker_notes stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Slides, apply this rule, and every set_speaker_notes call is checked against it from then on.
Questions about set_speaker_notes
Replaces a slide's speaker notes with the given text (empty string clears them). The tool resolves the slide's speakerNotesObjectId internally and rewrites that shape atomically — you pass the slide's object id, not the notes shape id. Notes are visible in the presenter view and exported by format txt; use \n for paragraphs. It is categorised as a Write tool in the Mcp Google Slides MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_speaker_notes accepts 3 parameters: text, presentation_id, slide_object_id. Required: text, presentation_id, slide_object_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Slides MCP server in PolicyLayer and add a rule for set_speaker_notes: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Google Slides. Nothing to install.
set_speaker_notes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_speaker_notes rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for set_speaker_notes. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
set_speaker_notes is provided by the Mcp Google Slides MCP server (@a1-x-tech/mcp-google-slides). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Slides, and thousands of servers like it.
This server
Across the catalogue