Skip to main content
Glama
JADRT22
by JADRT22

Related Servers

Alternatives to yt-transcript

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to search, analyze, and extract insights from YouTube videos including transcripts, visual frames, and benchmarks without requiring API keys. Supports semantic search across playlists, sentiment analysis, and visual content indexing with automatic fallback chains for reliable access.
      41
      81 npm
      35
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to retrieve YouTube transcripts, video info, channel video lists, and monitor channels for new uploads, with built-in prompt templates for summaries and industry signals—all without an API key.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Extract YouTube transcripts for AI agents, RAG pipelines, and LLM workflows. Supports any YouTube URL. Returns clean text or timestamped segments. No API keys required.
      1
      4
      MIT

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation3/5

    get_video_details_tool and get_video_info_tool overlap heavily, both returning title, channel and duration; the distinction (details adds description/comments, info adds upload date) is only implicit. get_transcript_tool and list_transcripts_tool are clearly separable, but the two metadata tools risk misselection.

    Naming Consistency5/5

    All four tools follow a consistent verb_noun_tool pattern (get_video_details_tool, get_transcript_tool, list_transcripts_tool, get_video_info_tool) with uniform snake_case. Naming is highly predictable.

    Tool Count4/5

    Four tools are well-scoped for a YouTube transcript/metadata server, each targeting a distinct operation. Slightly thin, and the count is partly inflated by two near-duplicate metadata tools that could be merged.

    Completeness4/5

    The surface covers listing available transcripts, fetching a transcript, retrieving metadata, and gathering description/comments, which spans the core domain lifecycle. No update/delete is needed for a read-only extractor, so coverage is solid with only minor gaps (e.g. no bulk or search operation).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues