Skip to main content
Glama

web-data-toolkit

by io.github.leekung125
OverviewDiscussionsAdmin

Get the full transcript of one or more YouTube videos as clean text.

youtube_transcript

Returns the transcript text for each video plus its language, whether the captions were auto-generated, word count, title and channel. Comma-separate up to 50 video URLs or ids. Videos with no captions come back with a status instead of text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoReturn every field as JSON instead of a compact summary. Default false.
urlYesYouTube URL or 11-character video id. Comma-separate up to 50.
langNoPreferred language codes in order, comma separated. Default en.
segmentsNoInclude timestamped segments as well as full text.
translateToNoTranslate the transcript into this language code.

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.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses output composition, the auto-generated captions indicator, and the edge case where no captions exist. It does not cover error conditions or output formatting details, but for a read-only transcript tool this is strong disclosure.

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 sentences, no filler, and every clause carries useful information. The output contents are listed first, followed by input format and an edge case. This is appropriately sized and well structured.

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?

For a public read operation with no output schema, the description covers the main return fields, batch input rules, and a notable failure behavior. It could mention the exact status values or error handling, but the description is sufficient for an agent 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 100%, so the schema already documents all parameters. The description reinforces the URL batch limit and adds context about missing captions, but does not add new meaning for raw, lang, segments, or translateTo.

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 precise verb and resource: it returns the transcript text for each video, plus language, auto-generation status, word count, title, and channel. This clearly distinguishes it from channel-level or review tools like youtube_channel_transcripts and app_store_reviews.

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 clear invocation context: pass up to 50 comma-separated video URLs or IDs, and videos without captions return a status. It does not explicitly name alternatives or exclusion conditions, but the scope is specific enough that an agent can infer when to use it.

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