Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{
  "tasks": {
    "list": {},
    "cancel": {},
    "requests": {
      "tools": {
        "call": {}
      },
      "prompts": {
        "get": {}
      },
      "resources": {
        "read": {}
      }
    }
  }
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_transcriptA

Get transcript text from a YouTube video.

Args: url: YouTube URL or video ID language: Language code (default: auto-detect) with_timestamps: Include timestamps in output

Returns: Dict containing video_id, language, and transcript text

get_video_infoA

Get metadata from a YouTube video.

Args: url: YouTube URL or video ID

Returns: Dict containing video metadata

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: one retrieves transcript text, the other fetches video metadata. There is no overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent 'get_' prefix with noun (transcript, video_info), forming a predictable verb_noun pattern.

Tool Count3/5

With only 2 tools, the server feels undersized for a YouTube integration. While the tools are focused, the count is on the low end for a typical MCP server.

Completeness2/5

The server covers only two basic reading operations, missing common YouTube actions like searching, listing comments, or managing playlists. Significant gaps exist for a comprehensive YouTube toolset.

Maintenance

ActivityInactive
ResponsivenessNo issues