Skip to main content
Glama
Sign In
yueying

yueying

by vsh5dvsch7-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_transcript

Read-onlyIdempotent

Search an already-watched video to locate when a specific phrase is spoken. Returns timestamps, surrounding transcript, and keyframe references for follow-up.

Instructions

Find where something is said in an already-watched video. Each hit shows the time, the surrounding sentences, and the nearest keyframe number and contact-sheet number so you can follow up with get_frame_at or get_transcript. Use this instead of paging the whole transcript when the user asks 'when does he mention X' or 'find the part about Y'.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to look for; separate alternatives with spaces (any term matches, more terms rank higher). Case-insensitive
videoYesvideo_id, results folder, or the path/URL given to watch_video
context_secondsNoSeconds of surrounding text to include around each hit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and idempotentHint. The description adds meaningful context on top: the 'already-watched' prerequisite and the exact per-hit result shape (time, surrounding sentences, keyframe number, contact-sheet number). It does not contradict annotations, though it leaves out result ordering and empty-result behavior.

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 purpose, then result contents, then usage guidance. Every clause earns its place and no information is repeated from the schema or annotations.

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?

Despite no output schema, the description tells the agent exactly what each hit returns and how to follow up with get_frame_at or get_transcript. Combined with the well-described parameters and annotations, the description gives the agent everything needed to select and invoke the tool 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 75% and the schema itself gives rich descriptions for video, query, and context_seconds. The tool description does not add parameter-level semantics and does not explain the undocumented limit parameter. This is a fair baseline score because the schema carries the semantic burden.

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?

The description states a specific action ('Find where something is said') targeting a specific resource ('an already-watched video' transcript) and describes the result contents. It clearly differentiates itself from get_transcript by framing itself as the targeted-search alternative to paging the full transcript.

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?

The description explicitly says to use this tool instead of paging the whole transcript when the user asks a specific mention question, with concrete example phrasing ('when does he mention X'). It also names follow-up tools, giving clear routing context. This is strong, actionable when-to-use guidance.

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