Skip to main content
Glama

read_deck_text

Extract slide titles and body text as plain strings for content review or narrative analysis; supports slide ranges and optional speaker notes.

Instructions

Lightweight text extractor: returns slide titles and body text as plain strings (~20x smaller than inspect_slide). Use for content review, narrative analysis, or any read-only text task. Supports slideRange and optional speaker notes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_deck_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideRangeNoSlide numbers, 1-based, e.g. "1", "1-5", "2,4,7". Omit for all slides.
includeNotesNoInclude speaker notes. Default: false.
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • changedInput schema / properties / slideRange / description
      Previous value: -"Slide range, e.g. \"0-5\", \"2,4,7\". Zero-based. Omit for all slides."New value: +"Slide numbers, 1-based, e.g. \"1\", \"1-5\", \"2,4,7\". Omit for all slides."
  2. First observedv0.6.0

TDQS

A4/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. It does disclose the return shape (titles plus body text as plain strings), the read-only nature, and the relative payload cost, but says nothing about what is omitted from the output (tables, charts, shape text, images) or about failure/permission behavior.

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 identity and the differentiator, with no redundant restatement of the schema. Every clause carries information.

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 zero-required-parameter read tool with full schema coverage and no output schema, the description covers purpose, cost, and return format adequately. The remaining gap is scope of extraction (which slide elements are and are not captured), which matters given sibling tools like read_shape_paragraphs and read_table.

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 slideRange syntax and the includeNotes default fully documented in the schema. The description only names the two parameters, adding no meaning beyond what the schema already provides, so baseline 3 applies.

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 (extract) and resource (slide titles and body text) and explicitly contrasts itself with the sibling inspect_slide on output size. An agent can pick this over inspect_slide without reading either 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 use cases (content review, narrative analysis, read-only text tasks) and implies the selection rule versus inspect_slide via the ~20x size comparison. It does not say when NOT to use it — e.g. when layout, geometry, table, or chart content is needed — which leaves one gap against the many deck siblings.

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