get_v2_trending — youtube MCP Tool Read-only
get_v2_trending
(get v2 trending) is one of 20 tools on the
youtube
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_v2_trending from your client
- Claude Code youtube get_v2_trending run in your project directory
- Claude Desktop youtube get_v2_trending ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor youtube get_v2_trending ~/.cursor/mcp.json
- VS Code youtube get_v2_trending .vscode/mcp.json
- Zed youtube get_v2_trending ~/.config/zed/settings.json
- Windsurf youtube get_v2_trending ~/.codeium/windsurf/mcp_config.json
- Cline youtube get_v2_trending ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI youtube get_v2_trending ~/.gemini/settings.json
- Grok youtube get_v2_trending .mcp.json (in your project root)
- ChatGPT youtube get_v2_trending Settings → Connectors → Advanced → Developer mode
- Claude.ai youtube get_v2_trending Settings → Connectors → Add custom connector
- LangChain youtube get_v2_trending pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http youtube https://mcp.jojapi.com/youtubeOther tools on this server
- get_v1_auto_complete
- get_v1_search
- get_v1_home
- get_v1_channel_details
- get_v1_channel_videos
- post_channel_videos
- get_v1_channel_playlists
- get_v1_channel_community
- get_v1_channel_channels
- get_v1_channel_search
- get_v1_video_details
- get_v2_video_details
- get_v1_video_comments
- get_v1_video_streaming_data
- get_v1_video_related_contents
- get_v1_playlist_details
- get_v1_playlist_videos
- get_v1_community_post_details
- get_v1_community_post_comments
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.