Skip to main content
Glama

Search transcripts

search_transcripts
Read-onlyIdempotent

Keyword search over full transcripts, returning matching paragraphs with a snippet, speaker, timestamp and a link to the exact paragraph. Use when search_facts finds nothing or you need the surrounding conversation: call get_transcript with show_slug, episode_slug and offset set to the hit's paragraph.

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_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
showNoOnly search this show: slug or title from list_shows
limitNoHow many to return, 1-20, default 10
queryYesKeywords, matched literally (stemmed full-text search, not semantic). Best with 2-4 distinctive words such as names, companies or terms, e.g. "Jensen Huang data centers". Filler and question words are ignored; results matching every keyword come first, then results matching some of them.
offsetNoHow many to skip, default 0. Pass next_offset from the previous page to get the next page.

Output Schema

NameRequiredDescriptionDefault
hintNo
noteNo
matchNo
totalYes
offsetYes
resultsYes
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is not carrying the safety burden; instead it adds useful behavior: what a result contains and that matching is keyword-based rather than semantic. It stops short of stating result ordering or paging limits ("every keyword first, then some"), which the schema covers instead.

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?

Two sentences, zero filler, with the purpose and return shape front-loaded and the routing/next-step guidance packed into the second. No restating of the title or schema.

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?

An output schema exists so return values needn't be re-explained, yet the description still summarizes them well, and the follow-up path to get_transcript closes the loop. Only minor gap is that paging behavior and result ranking are left entirely to the 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 parameters are already fully documented, and the description adds little about its own parameters beyond reinforcing the keyword nature of `query`. Its parameter-related sentence actually describes get_transcript's arguments (show_slug, episode_slug, offset), which is cross-tool guidance rather than added meaning for this tool's schema.

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 ("Keyword search over full transcripts") and pins down the output shape: matching paragraphs with snippet, speaker, timestamp and deep link. The word "keyword" plus the contrast with search_facts makes it distinguishable from the sibling fact-search tool without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("when search_facts finds nothing or you need the surrounding conversation") and a concrete follow-up action naming get_transcript and how to pass the hit's paragraph as an offset. When-to-use and the next step are both spelled out rather than inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources