Skip to main content
Glama

duplicate_slide

Copies a slide with all content, formatting, and notes intact, letting you reuse designed template slides and edit the copy. Supports multiple copies and insertion at any position.

Instructions

Copy an existing slide, keeping all of its content and formatting.

This is the way to reuse a corporate template's designed slides: duplicate the slide whose layout suits your next section, then edit the copy's text with manage_text / populate_placeholder. add_slide builds a bare slide from a layout and gets you none of the template's artwork, so prefer duplicating when the template already contains a slide that looks right.

slide_index: 0-based index of the slide to copy. insert_after: 0-based index the copy is placed after; omit to append the copy (or copies) to the end of the deck. count: how many copies to make, for a section that repeats — the copies land consecutively.

Pictures are shared with the original (same bytes, no size cost); charts, SmartArt and embedded objects are cloned, so editing the copy's chart does not change the original's. Speaker notes are copied. Returns "new_slide_indexes" — read them before editing, since inserting in the middle shifts every later slide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
slide_indexYes
insert_afterNo
presentation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.6.0

TDQS

A5/5.0
Behavior5/5

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

With no readOnly/destructive annotations, the description carries the full behavioral disclosure burden. It does so thoroughly: pictures are shared, charts/SmartArt/embedded objects are cloned, speaker notes are copied, inserted copies shift later slide indexes, and the return value is named. This is exactly the context an agent needs to anticipate side effects.

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?

The description is information-dense but well organized: the core purpose comes first, followed by usage guidance, parameter semantics, and then important side effects and return-value warnings. No sentence is wasted, and critical caveats about index shifting are placed near the return-value note where they matter most.

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

Completeness5/5

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

Given the lack of annotations and 0% schema parameter descriptions, the description covers all essential operational context: what gets copied, what is shared versus cloned, how positioning works, how multiple copies behave, and what to read from the return value. The presence of an output schema means the return structure itself does not need to be spelled out here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It fully explains slide_index as 0-based, insert_after as 0-based with append-on-omit semantics, and count as the number of consecutive copies. These details go well beyond the bare schema and make the parameters self-documenting.

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?

The description opens with a specific verb and resource: 'Copy an existing slide, keeping all of its content and formatting.' This clearly distinguishes the tool from related operations like add_slide and copy_slide_between_presentations, even without comparing schemas.

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

Usage Guidelines5/5

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

The description explicitly tells when to prefer this tool over add_slide, pointing out that add_slide builds a bare slide and loses template artwork. It also explains when count is useful ('for a section that repeats'), giving an agent concrete criteria for selecting this tool.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/photonn/dial-pptx-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server