Skip to main content
Glama

edit_slide_zip

Update multiple files inside a slide ZIP and reimport them in one operation. Modify existing XML or add new files such as charts, with automatic Content_Types registration for new chart files.

Instructions

Update multiple files in the slide zip and reimport in a single operation. Accepts a map of { path: content } — can modify existing files or add new ones (e.g. chart XML + rels). Auto-registers Content_Types for new chart files. Use read_slide_zip first to get the current content.

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>",
      "files": "<files>"
    },
    "name": "edit_slide_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesMap of { zipPath: newContent }. Can include existing paths (to modify) or new paths (to add). Example: { "ppt/slides/slide1.xml": "<p:sld>...</p:sld>", "ppt/charts/chart1.xml": "<c:chartSpace>...</c:chartSpace>" }
slideYesSlide number, 1-based (slide 1 = first slide)
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 / slide
      Added value: +{
      +  "description": "Slide number, 1-based (slide 1 = first slide)",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based slide index",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slideIndex",
      -  "files"
      -]New value: +[
      +  "slide",
      +  "files"
      +]
  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?

With no annotations, the description carries the full burden. It usefully discloses that it reimports in a single operation and auto-registers Content_Types for new chart files, which is a real side effect. It does not say that supplied content fully replaces existing file content, nor whether edits are reversible or what happens on invalid XML.

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 short sentences, front-loaded with the operation and payload shape, followed by the side effect and the prerequisite. No redundant or filler wording.

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 nested-object mutation tool with no annotations and no output schema, the description covers payload shape, side effects, and prerequisites well. The remaining gap is that nothing is said about the result of the operation (success/failure reporting), which matters because there is no output schema.

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 all three parameters are already documented. The description adds genuine semantics for the nested 'files' map (existing paths modify, new paths add, chart XML + rels example), but says nothing extra about slide or presentationId beyond the schema; per the high-coverage baseline this lands at 3-4.

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 ('Update multiple files in the slide zip and reimport') and scopes it as a batch operation over a { path: content } map. It implicitly contrasts with the single-file edit_slide_xml and names read_slide_zip, but never explicitly states which sibling to pick for single-file edits.

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 a concrete prerequisite workflow: 'Use read_slide_zip first to get the current content,' which tells the agent the correct call order. It does not state when to avoid this tool (e.g. when a dedicated tool like edit_slide_chart or edit_speaker_notes would be safer).

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