Skip to main content
Glama

web-data-toolkit

by io.github.leekung125
OverviewDiscussionsAdmin

Search YouTube, or list a channel or playlist, and return every video with its transcript.

youtube_channel_transcripts

Enumerates the newest videos of a channel, @handle or playlist and returns each video's metadata and transcript in a single call. Pass "search: your query" instead of a channel to go straight from a question to transcripts without knowing which creator to ask - the top results come back with full transcripts. Useful for building a corpus on a topic or from one creator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNoHow many of the newest videos to fetch. Default 25, max 500.
rawNoReturn every field as JSON instead of a compact summary. Default false.
langNoPreferred caption language. Default en.
sourceYes@handle, channel URL or id, a playlist URL, or "search: your query" to search YouTube.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / raw
      Added value: +{
+  "description": "Return every field as JSON instead of a compact summary. Default false.",
+  "type": "boolean"
+}
    • removedInput schema / raw
      Removed value: -{
-  "description": "Return every field as JSON instead of a compact summary. Default false.",
-  "type": "boolean"
-}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It does disclose key traits like returning the newest videos, returning metadata plus transcripts in one call, and search returning top results. However, it omits operational details such as rate limits, authentication requirements, behavior when transcripts are unavailable, or error handling.

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?

The description is concise at three sentences and front-loads the core capability before explaining the search mode and use case. The final sentence about corpus building is useful but slightly optional; otherwise there is no wasted text.

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?

The tool has no output schema and no annotations, so the description must be self-sufficient. It covers the main source modes and the batch nature, but it does not mention the single-video alternative youtube_transcript, transcript availability caveats, return format details beyond 'metadata and transcript', or potential limits/errors. This leaves important edge cases to inference.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining the 'search: your query' source syntax and when to use it. Other parameters (max, raw, lang) are adequately documented in the schema itself.

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 action and resource: 'Enumerates the newest videos of a channel, @handle or playlist and returns each video's metadata and transcript in a single call.' It also explains the 'search:' mode, clearly distinguishing this bulk transcript tool from the single-video sibling youtube_transcript.

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 description gives practical guidance: use search when you don't know the creator, and use the tool for building a corpus from one topic or creator. It does not explicitly tell the agent when not to use it or point to youtube_transcript for single-video needs, so it falls just short of full exclusion guidance.

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

All web-data-toolkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources