Skip to main content
Glama

edit_speaker_notes

Set or replace speaker notes on one or more slides using markdown text; converts content to OOXML and applies it during live presentations.

Instructions

Set speaker notes on one or more slides. Accepts markdown text (paragraphs, bold, italic). Converts to OOXML server-side and injects via single-slide reimport. Replaces all existing notes on the specified slides.

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

Input Schema

NameRequiredDescriptionDefault
notesYesArray of slide notes to set.
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • addedInput schema / properties / notes / items / properties / slide
      Added value: +{
      +  "description": "Slide number, 1-based (slide 1 = first slide)",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / notes / items / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based slide index",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / properties / notes / items / required
      Previous value: -[
      -  "slideIndex",
      -  "text"
      -]New value: +[
      +  "slide",
      +  "text"
      +]
  2. First observedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose valuable behavior: server-side markdown-to-OOXML conversion, single-slide reimport injection, and that all existing notes on the target slides are destroyed. It omits any mention of permissions, whether the reimport is atomic or can partially fail, and what the caller gets back on success.

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?

Three short sentences with the destructive-replacement warning front-loaded alongside the core action. Minor redundancy in re-listing markdown constructs that the schema already enumerates, but nothing is wasted.

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 two-parameter tool with no output schema and full schema coverage, the description covers the action, the format, the internal mechanism, and the destructive side effect. Only the return value and failure semantics are left unspecified, which is a small gap at this complexity.

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 100%, so both parameters are already documented in the schema, including markdown support, the empty-string clearing behavior, and 1-based slide numbering. The description's markdown formatting note largely duplicates the schema rather than adding new semantics, so baseline 3 applies.

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 and resource ('Set speaker notes on one or more slides'), which cleanly implies the write counterpart to read_speaker_notes. It does not explicitly name or contrast with any sibling, but the read/write split against the sibling list is unambiguous.

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 implied by the verb and the caution that existing notes are replaced, but there is no explicit guidance on when to use this versus edit_slide_xml or edit_shape_paragraphs, nor any stated prerequisite such as needing a presentationId or an active deck. An agent can infer usage but is not routed.

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