Skip to main content
Glama

TranscriptLab

Search a cached transcript

transcriptlab_search_transcript
Read-onlyIdempotent

Search, quote, or slice a transcript already delivered to this account. Use for "find the part where...", keyword or regex lookup, or paginating a long transcript into chunks. It never starts a fetch and never charges transcript credits, so it only works on a video already cached here: deliver it first with transcriptlab_get_transcript if it is not. mode chooses the behavior: keyword matches terms, regex matches a pattern, chunk returns sequential sections.

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>",
      "mode": "<mode>"
    },
    "name": "transcriptlab_search_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL or 11-character video ID.
langNo
modeYeskeyword matches terms, regex matches pattern, chunk returns sequential sections.
typeNo
flagsNoOptional regular expression flags.
termsNoRequired in keyword mode.
patternNoRequired in regex mode.
translateNo
max_tokensNo
context_charsNo
target_tokensNo
case_sensitiveNo
overlap_snippetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts not in the annotations: it never starts a fetch, never charges transcript credits, and only works against previously cached content. It stops short of describing result shape or pagination mechanics, but since no output schema exists that gap is modest rather than fatal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four purposeful sentences, front-loaded with what the tool does and the cached-only constraint, followed by usage triggers, the prerequisite, and mode semantics. The only redundancy is the mode sentence, which largely restates the schema's mode enum description.

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?

Given 13 parameters, low schema coverage, and no output schema, the definition covers the critical prerequisites and mode selection well. However, it says nothing about how the pagination/chunking parameters (max_tokens, target_tokens, overlap_snippets) behave, which is exactly the complexity an agent needs described when slicing a long transcript.

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 only 38% across 13 parameters, so the description must carry the load, but it only elaborates on mode (repeating the schema's own enum description nearly verbatim). Parameters like lang, type, flags, translate, max_tokens, target_tokens, context_chars, case_sensitive, and overlap_snippets get no meaning from the description, leaving the agent to guess how chunking and token budgets interact.

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 opens with a specific verb set and resource: "Search, quote, or slice a transcript already delivered to this account." It immediately distinguishes itself from fetch-style siblings by stating it only operates on cached transcripts, so an agent can tell it apart from transcriptlab_get_transcript 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?

It gives concrete usage triggers ("find the part where...", keyword or regex lookup, paginating a long transcript) and an explicit prerequisite with the exact sibling to call first: "deliver it first with transcriptlab_get_transcript if it is not." The mode sentence further routes the agent among keyword, regex, and chunk behaviors, leaving little to inference.

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.