Skip to main content
Glama

YouTube Transcript & Search MCP Server

by com.transcriptout

Search within a playlist

search_playlist_videos
Read-only

Find videos inside a playlist by a substring of the title (case-insensitive). YouTube has no native playlist search, so this scans up to 500 playlist items. truncated=true means there may be more matches beyond the scanned window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSubstring to match in the video title
idYesPL... playlist id or URL
limitNoMax matches to return, 1-100 (default 30)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
truncatedNo

TDQS

A4.7/5.0
Behavior5/5

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

Adds meaningful behavior beyond the readOnlyHint annotation: case-insensitive matching, a fixed 500-item scan window, and the meaning of truncated=true. This sets accurate expectations for an agent, including the possibility of missing matches.

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 compact sentences with no filler. The core action is front-loaded, and the truncation caveat is stated in exactly the right amount of detail.

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?

With an output schema present and read-only annotations provided, the description covers the key remaining facts an agent needs: substring semantics, playlist limit, and truncation behavior. Nothing important is missing.

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?

The schema already describes all parameters, so the baseline is 3. The description adds extra value by specifying case-insensitive matching and explaining the scan limit, which influences the output and interpretation of matches.

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?

States a specific verb and resource: find videos inside a playlist by substring of the title, case-insensitively. This clearly distinguishes it from siblings like list_playlist_videos and search_youtube.

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?

Establishes the context clearly: use it for substring search within a playlist, and explains that YouTube provides no native playlist search. It could go further by naming explicit alternatives, but the implied usage is sufficiently clear.

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

All YouTube Transcript & Search MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools target a distinct resource and action: search, list, metadata, transcript, job lifecycle, and credits. The get_transcripts_job / get_transcripts_result / get_transcripts_results trio is easy to blur at first glance, but the descriptions clearly differentiate job status, one result, and paged results.

Naming Consistency4/5

The set mostly follows a predictable verb_noun pattern: get_, list_, search_, submit_, cancel_. The main deviation is latest_channel_videos, which uses an adjective instead of a verb, and the result/results pair is mildly confusing, but overall naming is coherent and easy to navigate.

Tool Count5/5

14 tools is well within the sweet spot for a server with this scope. Each tool serves a clear niche: video lookup, metadata, single transcripts, batch jobs, and search are all represented without unnecessary or redundant tools.

Completeness5/5

The server provides full coverage of the transcript and search workflow: search YouTube, list channel/playlist videos, fetch or batch-fetch transcripts, check job progress/credits, and read results. There are no obvious missing operations that would force an agent into a dead end.

Resources