Skip to main content
Glama
bendelpino

YouTube MCP Server

by bendelpino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
YOUTUBE_API_KEYYesYour YouTube Data API v3 key from Google Cloud Console

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_youtube_videosB
Search YouTube videos based on a search term.

Args:
    search_term: The search query for YouTube videos
    num_videos: Number of videos to retrieve (default: 5, max: 50)

Returns:
    List of video information dictionaries containing title, video_id, channel, description, etc.
get_youtube_transcriptB
Get the transcript of a YouTube video.

Args:
    video_url_or_title: YouTube video URL or video ID

Returns:
    Dictionary containing the video transcript and metadata

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: one retrieves transcripts for specific videos, while the other searches for videos based on queries. There is no overlap in functionality, making it impossible for an agent to confuse them.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with clear, descriptive names: get_youtube_transcript and search_youtube_videos. The naming convention is uniform and predictable throughout the set.

Tool Count2/5

With only two tools, this server feels severely underpowered for YouTube integration. Key operations like uploading videos, managing playlists, getting video details, or interacting with comments are missing, making the surface too thin for meaningful YouTube automation.

Completeness2/5

The toolset is highly incomplete for a YouTube server. While transcript fetching and video search are useful, there are major gaps: no CRUD operations for videos/channels/playlists, no interaction capabilities (likes/comments), and no metadata retrieval beyond search results. This will cause significant agent failures in typical YouTube workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources