Skip to main content
Glama

add_slide

Insert a new PowerPoint slide from a selected layout at a chosen position, pre-fill placeholder text, and return named placeholder shapes for editing.

Instructions

Add a new slide from a layout at a specific position, with placeholder text pre-filled and shapes renamed to layout names. Use inspect_layouts to find available layout names and placeholder names. Returns the new slide number (1-based) and its placeholder shapes with semantic names.

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": {
      "layoutName": "<layoutName>"
    },
    "name": "add_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionNo1-based insertion position (position 1 = the new slide becomes the first slide; existing slides shift right). Default: append at end.
layoutNameYesLayout name from inspect_layouts (e.g. "Title and Content", "Section Header"). Case-insensitive match. Layouts starting with "_" are rejected (technical layouts).
placeholdersNoMap of layout placeholder name → text content. E.g. {"section_title": "Backup Slides", "section_subtitle": "Evidence & appendix"}. Names must match layout placeholder names from inspect_layouts.
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.1
    • changedInput schema / properties / position / description
      Previous value: -"Zero-based target slide index. The new slide is inserted at this position (existing slides shift right). Default: append at end."New value: +"1-based insertion position (position 1 = the new slide becomes the first slide; existing slides shift right). Default: append at end."
    • changedInput schema / properties / position / minimum
      Previous value: -0New value: +1
  2. First observedv0.6.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden well: it names the mutation (adding a slide, shifting existing slides via position), the automatic behaviors (placeholder pre-fill, shape renaming to semantic names), and the return payload. It omits failure modes beyond the schema-level '_' layout rejection, and doesn't mention permissions or whether the change is undoable.

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?

Three tight sentences: what it does first, prerequisite second, return value last. No filler, no restatement of the name, and the agent's next action (call inspect_layouts) is unambiguous.

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?

No output schema exists, and the description compensates by stating the return shape (1-based slide number plus placeholder shapes with semantic names). Combined with 100% schema coverage on inputs and the inspect_layouts pointer, an agent has everything needed to invoke it correctly; only error handling is left implicit.

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 description coverage is 100%, so parameters are already fully documented with examples and edge cases (1-based position, case-insensitive layout names, '_' rejection). The description adds only the high-level notion of position and placeholder pre-fill, which is baseline-level value rather than new semantic detail.

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?

States a specific verb and resource ('Add a new slide from a layout at a specific position') plus the scope of side effects (placeholder text pre-filled, shapes renamed to layout names). This clearly separates it from siblings like duplicate_slide or copy_slides, which clone existing slides rather than instantiating a layout.

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

Usage Guidelines4/5

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

Explicitly routes the agent to inspect_layouts for valid layout and placeholder names, which is the key prerequisite for using this tool successfully. It doesn't state when NOT to use it (e.g. prefer duplicate_slide to copy an existing slide), so it falls short of the full when/when-not/alternatives standard.

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