Skip to main content
Glama

copy_slides

Copies a slide between open presentations server-side, keeping Base64 data out of Claude context and inserting it into the destination in one operation.

Instructions

Copies slides between two open presentations entirely server-side — the Base64 data never enters Claude context. Exports from the source presentation and inserts into the destination in a single operation. Both presentations must be connected to the bridge. Requires PowerPointApi 1.8.

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": {
      "sourceSlide": "<sourceSlide>",
      "sourcePresentationId": "<sourcePresentationId>",
      "destinationPresentationId": "<destinationPresentationId>"
    },
    "name": "copy_slides"
  }
}

Input Schema

NameRequiredDescriptionDefault
formattingNoFormatting mode. Default: KeepSourceFormatting.
sourceSlideYesSlide number, 1-based (slide 1 = first slide), to copy from the source presentation
targetSlideIdNoInsert after this slide ID in destination (format: "nnn#" or "#mmmmmmmmm" or "nnn#mmmmmmmmm"). If omitted, inserts at the beginning.
sourcePresentationIdYesSource presentation ID from list_presentations
destinationPresentationIdYesDestination presentation ID from list_presentations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • addedInput schema / properties / sourceSlide
      Added value: +{
      +  "description": "Slide number, 1-based (slide 1 = first slide), to copy from the source presentation",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / sourceSlideIndex
      Removed value: -{
      -  "description": "Zero-based slide index to copy from the source presentation",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "sourceSlideIndex",
      -  "sourcePresentationId",
      -  "destinationPresentationId"
      -]New value: +[
      +  "sourceSlide",
      +  "sourcePresentationId",
      +  "destinationPresentationId"
      +]
  2. First observedv0.6.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden and it does deliver real value: server-side execution, Base64 payload never entering context, and export+insert as a single operation (implying atomicity). It does not say whether the source slide is left intact, what happens if the destination call fails midway, or what the response contains — gaps that matter for a mutation tool with zero annotation coverage.

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 tight sentences, front-loaded with the most decision-relevant fact (it happens server-side and costs no context). The middle sentence about export/insert mildly restates the copying action but earns its place by conveying atomicity; nothing else is padding.

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?

Covers prerequisites and execution model well, and with no output schema there is no return-value obligation, but for a destructive-capable cross-document mutation it never states whether the source is preserved or what the agent gets back on success/failure. Adequate, not complete.

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%: every one of the five params, including the formatting enum default and the three targetSlideId ID formats, is documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline 3 is correct.

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 (copies slides) plus the crucial scope qualifier 'between two open presentations,' which separates it from duplicate_slide (same-deck duplication) and from transform_slide. An agent can pick this tool without opening a schema.

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?

Gives concrete preconditions — both presentations must be connected to the bridge and PowerPointApi 1.8 is required — which is exactly the kind of gating information an agent needs before attempting the call. It stops short of naming the same-presentation alternative (duplicate_slide) or saying when-not to use it, so it lands at 4 rather than 5.

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