Skip to main content
Glama

seek_to_text

Jumps video playback to the point where a phrase is spoken. Searches subtitles, optionally filters by speaker, and seeks just before that line so the sentence starts from its beginning.

Instructions

Jump playback to where a phrase is spoken. Finds the phrase in the subtitles (optionally filtered by speaker) and seeks just before that line, so the sentence is heard from its start. This is the 'skip to the part where they talk about X' tool.

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

Input Schema

NameRequiredDescriptionDefault
fileNoOptional path to a video or subtitle file; defaults to the playing file
queryYesPhrase to jump to
speakerNoOptional speaker filter
occurrenceNoWhich occurrence, 1-based (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the pre-roll behavior ("seeks just before that line, so the sentence is heard from its start"), which is non-obvious. It does not say what happens when the phrase is not found, whether subtitles must be loaded or a track selected, or whether playback state changes.

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 core action, then the mechanism, then a memorable use-case gloss. No redundancy or filler.

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?

No output schema or annotations exist, but the description covers the mechanic and the seek positioning well enough that an agent can call it correctly. The missing piece is failure behavior (no match, missing subtitles) and multi-occurrence semantics.

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 all four parameters (file, query, speaker, occurrence) are already documented in the schema. The description adds only that speaker filtering exists; it says nothing about occurrence disambiguation or file defaulting beyond what the schema states. Baseline 3 applies.

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?

Names a concrete verb and resource: it finds a spoken phrase in subtitles and seeks playback to it. The closing line ("the 'skip to the part where they talk about X' tool") frames it as content-based seeking as opposed to time- or chapter-based seeking, though it never names the siblings it differs from (seek, chapter_seek).

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?

The use case is clear and grounded: when you want to hear the sentence containing a phrase, use this tool. It gives no exclusion guidance, though — nothing about what to do when the phrase is absent, or when chapter_seek/seek would be preferable.

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