Skip to main content
Glama

library_transcript_search

Search spoken dialogue across every video with a sidecar or cached transcript. Returns matching cues with video path, title, and timestamp so you can open the exact line in the player.

Instructions

Search spoken dialogue across every video in the media library that has a sidecar (.srt/.vtt) or cached transcript. Returns each matching cue with its video path, title, and timestamp so you can immediately open that video at that line with play (passing file and seek).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return (1-200, default 20)
queryYesPhrase to search for across the library (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses coverage limits (only videos with a sidecar or cached transcript are searchable), and it describes the return shape (each matching cue plus video path, title, and timestamp). It stops short of noting ordering, empty-result behavior, or that it is a read-only operation, but nothing is misleading.

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, front-loaded with the scope constraint, and the second sentence packs both the return format and the workflow hand-off to `play`. No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description still explains what a result looks like (cue, video path, title, timestamp) and how to act on it. Combined with full schema coverage of both parameters, an agent has everything needed to call this correctly.

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 both `query` (case-insensitive phrase) and `limit` (1-200, default 20) are already documented. The description reinforces that the phrase is matched against spoken dialogue library-wide but adds no format or syntax detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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: search spoken dialogue across every video in the media library, with an explicit scope qualifier (only videos with a sidecar .srt/.vtt or cached transcript). An agent can distinguish this from a filename/metadata search like library_search. It does not, however, explicitly contrast itself with the similarly named search_transcript sibling, so the differentiation is inferred 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 Guidelines4/5

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

Gives a clear use context (finding a spoken line across the whole library) and a concrete follow-on action: open the hit with `play` by passing `file` and `seek`. It does not state exclusions or name an alternative for the single-video case, so an agent must infer when search_transcript is the better choice.

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

Deploy Server

Other Tools