Skip to main content
Glama

search_text

Find text across presentation slides, shapes, table cells, and speaker notes using substring or regex matching. Returns matching shapes and slide context so you can locate content by range.

Instructions

Search for text across all slides (or a slide range) in the presentation — like grep for slides. Searches shape text, table cells, and speaker notes. Returns matching shapes with context at the chosen level. Case-insensitive substring by default; supports regex.

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": {
      "query": "<query>"
    },
    "name": "search_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesText to search for. Plain substring by default, or a regex pattern when regex=true.
regexNoTreat query as a regular expression. Default: false (plain substring).
contextNoResult detail level. "shape" (default): matching shapes with text. "slide": all shapes on matching slides with matched markers. "none": just matching slide indices.
slideRangeNoOptional slide range to search, e.g. "1-5" or "2-8". Slide numbers are 1-based. Omit to search all slides.
includeNotesNoSearch speaker notes in addition to slide content. Default: true.
caseSensitiveNoCase-sensitive search. 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: -"Optional slide range to search, e.g. \"0-4\" or \"2-7\". Zero-based. Omit to search all slides."New value: +"Optional slide range to search, e.g. \"1-5\" or \"2-8\". Slide numbers are 1-based. Omit to search all slides."
  2. First observedv0.6.0

TDQS

A3.5/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 whole burden. It does disclose meaningful behavior: what surfaces are searched, that matching is case-insensitive substring by default with regex support, and that results are returned 'at the chosen level'. It never states the operation is read-only/non-mutating, and says nothing about limits, result size, or what happens with an invalid regex — gaps that matter for a 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 short sentences, front-loaded with the core action and scope, and every clause carries information (surfaces searched, return shape, matching semantics). The grep analogy earns its place as a fast mental model; no filler or repetition.

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 seven-parameter read tool with full schema coverage and no output schema, the description gives enough to call it correctly: what is searched, how matching behaves, and the granularity of results. The only meaningful omissions are the non-mutating guarantee and behavior on invalid regex or empty results, which an agent would otherwise have to discover by trial.

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%, so every one of the seven parameters is already documented inline, including enum values for context and defaults for regex, includeNotes, and caseSensitive. The description echoes the searchable surfaces and default matching mode but adds no new syntax, constraints, or edge-case meaning beyond the schema — the baseline of 3 is appropriate.

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 with scope: 'Search for text across all slides (or a slide range) in the presentation', plus the grep analogy and the searched surfaces (shape text, table cells, speaker notes). This separates it in practice from search_document and find_in_range, but it never names those siblings explicitly, so the differentiation is inferred from the scope wording rather than stated.

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?

The 'like grep for slides' analogy and the slide-range mention imply when to reach for this tool, and the default matching semantics are spelled out. However, there is no explicit guidance on when NOT to use it versus read_deck_text, scan_slide, or search_document, and no note on prerequisites (e.g., needing a connected presentation) beyond what the schema says.

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