Skip to main content
Glama
Sign In

YouTube Transcript + YouTube Search MCP

by com.getyoutubetranscript
OverviewDiscussionsAdmin

Get Related Videos

get_related_videos
Read-only

Use this when the user wants videos similar to one they shared, or asks 'what else should I watch' after a video. Returns the videos YouTube suggests next to it, each with title, video ID, link, channel, views, age and length. Pass a result's video ID to get_youtube_transcript for what it says.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video_url": "<video_url>"
    },
    "name": "get_related_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_urlYesYouTube URL (full or short) or an 11-character video ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and open-world behavior, and the description adds value beyond them by enumerating the returned fields (title, video ID, link, channel, views, age, length), which matters because no output schema exists. It also discloses the natural follow-up chain to get_youtube_transcript. It stops short of noting result count, ordering, or rate/availability caveats.

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, front-loaded with the trigger condition, then return shape, then the follow-up pointer. No filler or restatement of the tool name.

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?

For a single-parameter read tool with no output schema, the description supplies the use case, the exact return fields, and the downstream chaining tool. An agent has everything needed to call it and route its results without opening the schema.

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 coverage is 100% and the single video_url property already documents that it accepts a full/short URL or an 11-character video ID. The description's mention of passing a result's video ID to another tool indirectly confirms ID acceptance but adds no new syntax or validation detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns the videos YouTube suggests alongside a given video, each with a concrete field list. It implicitly separates itself from search_youtube by framing the input as an existing video ('similar to one they shared'), though it never names that sibling as the alternative.

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?

Gives two concrete triggers — the user wants videos similar to one they shared, or asks 'what else should I watch' after a video. Clear context for invocation, but no explicit exclusions (e.g., 'use search_youtube instead when the user has no seed video').

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

All YouTube Transcript + YouTube Search MCP 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