Skip to main content
Glama

read_slide_xml

Retrieves a slide's raw OOXML or a specific shape's XML by ID, helping inspect PowerPoint slide structure and properties.

Instructions

Read the full raw OOXML of a slide, or filter to a specific shape. Returns the slide's ppt/slides/slide1.xml content. Use with the /pptx skill's OOXML knowledge to understand the XML structure.

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": "read_slide_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideYesSlide number, 1-based (slide 1 = first slide), from scan_slide results
shapeIdNoOptional shape ID to filter to. If provided, returns only that shape's <p:sp> element.
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), from scan_slide results",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based slide index from scan_slide results",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slideIndex"
      -]New value: +[
      +  "slide"
      +]
  2. First observedv0.6.0

TDQS

B3.4/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 does disclose that this is a read of raw XML, what content is returned, and that shapeId narrows the output to a single <p:sp> element. It omits practical traits such as how large the full-slide XML output can be, whether shapeId filters before or after serialization, or what happens on an invalid slide/shape reference.

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 short sentences with the primary purpose and the return payload front-loaded, and the filtering behavior immediately after. Nothing is padded, though the third sentence is advisory context rather than definitional content.

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?

For a three-parameter read tool with a fully documented schema and no output schema, the description adequately covers purpose, return payload, and the optional shape filter. It is thin on the two things most likely to trip an agent: when this beats the many sibling XML/inspection tools, and the practical size cost of reading a whole slide's raw XML.

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%, with slide, shapeId, and presentationId each documented in the schema itself, so the baseline is 3. The description restates the shape-filter behavior but adds no format or usage detail (e.g., how to obtain a shape ID) beyond what the schema already says.

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?

"Read the full raw OOXML of a slide, or filter to a specific shape" gives a concrete verb plus resource and states the two operating modes, and the second sentence names the exact artifact returned (ppt/slides/slide1.xml). It stops short of differentiating itself from close siblings such as read_slide_zip, edit_slide_xml, or inspect_slide, so an agent must infer which XML-reading tool it wants.

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 with the /pptx skill's OOXML knowledge to understand the XML structure" implies the intended context (low-level XML inspection during the /pptx workflow) but never states when to prefer this over read_shape_paragraphs, inspect_slide, or read_slide_zip, and gives no exclusions or prerequisites such as needing a slide number from scan_slide first.

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