Skip to main content
Glama

duplicate_slide

Copy a slide within the same PowerPoint presentation by exporting and reimporting it at a chosen position, keeping all data server-side.

Instructions

Duplicate a slide within the same presentation. Exports the slide and reimports it at the specified position. Data stays server-side. The reimport makes PowerPoint view jump to the first 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": {
      "slide": "<slide>"
    },
    "name": "duplicate_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideYesSlide number, 1-based (slide 1 = first slide), of the slide to duplicate
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.
insertAfterSlideNo1-based slide number to insert the duplicate after. Default: same as slide (duplicate appears right after the source).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.1
    • removedInput schema / properties / insertAfter
      Removed value: -{
      -  "description": "Zero-based slide index to insert the duplicate after. Default: same as slideIndex (duplicate appears right after the source).",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • addedInput schema / properties / insertAfterSlide
      Added value: +{
      +  "description": "1-based slide number to insert the duplicate after. Default: same as slide (duplicate appears right after the source).",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / slide
      Added value: +{
      +  "description": "Slide number, 1-based (slide 1 = first slide), of the slide to duplicate",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based index of the slide to duplicate",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slideIndex"
      -]New value: +[
      +  "slide"
      +]
  2. First observedv0.6.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it explains the underlying export/reimport mechanism, notes that data stays server-side, and warns of a concrete side effect (PowerPoint view jumps to the first slide). It does not say what is returned, or whether notes/animations/embedded media survive the round-trip, which matters for a fidelity-sensitive operation.

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?

Four compact sentences, front-loaded with the core action and then the mechanism, privacy note, and caveat. Each sentence carries distinct information, with only minor redundancy between 'exports and reimports' and 'the reimport makes...'.

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

Completeness3/5

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

No output schema, no annotations, and the description never indicates what the call returns (e.g., the new slide's index), which an agent needs in order to reference or further operate on the duplicate. The mechanism and side-effect disclosures are good, but this return-value gap leaves the definition incomplete for chaining into follow-up calls.

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 the schema already defines slide, presentationId, and insertAfterSlide. The phrase 'at the specified position' loosely maps to insertAfterSlide but adds no format, default, or edge-case detail beyond the schema text.

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 ('Duplicate a slide within the same presentation') plus the mechanism (export/reimport). The scoping phrase 'within the same presentation' implicitly distinguishes it from cross-presentation copying, but the closest sibling copy_slides is never named, so the differentiation is only partial.

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?

Use for duplicating a single slide in the current presentation is implied by the name and description, but there is no explicit when-to-use guidance and no routing toward copy_slides or add_slide when the intent differs (e.g., copying across decks or creating a blank slide).

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