Skip to main content
Glama

find_in_video

Find where a topic is said in a video using comma-separated terms; returns timestamped caption lines with context and optional frames at each hit.

Instructions

Find WHERE a topic is said in a video. query: comma-separated terms (any match). Returns timestamped caption lines (with a little context). frames=True also returns the video frame at each hit.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
langNoauto
queryYes
widthNo
framesNo
max_hitsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/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 add real value: it discloses the return shape (timestamped caption lines with a little context) and the frames=True side effect (a video frame per hit). It omits cost/latency implications of frame extraction, auth requirements, and how hits are ordered or capped.

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, zero filler, with the core purpose front-loaded and the two most decision-relevant parameters (query, frames) called out in place. Nothing to trim.

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

Completeness3/5

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

For a 6-parameter tool with no annotations and no output schema, the description covers the return format well but leaves four parameters (url, lang, width, max_hits) undefined, so an agent cannot confidently set max_hits or lang from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, and the description only explains query (comma-separated, any-match OR semantics) and frames. The url, lang, width, and max_hits parameters are undocumented in both schema and description, leaving half the surface ambiguous.

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 ('Find WHERE a topic is said in a video'), which implicitly separates it from full-transcript siblings like transcribe_video or video_transcript. The scope word 'WHERE' makes the localization intent clear, though no sibling is named explicitly.

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 phrase 'Find WHERE a topic is said' implies the search/targeted-lookup use case versus a full transcript, but the description never says when to prefer this over transcribe_video or watch_video, nor any exclusions or prerequisites.

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