Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List YouTube channel videos

youtube_channel_videos_list
Read-onlyIdempotent

List long-form videos from a YouTube channel by ID or handle, excluding Shorts. Sort by recency or popularity and paginate results to browse channel content.

Instructions

List long-form videos from a YouTube channel (not Shorts — use youtube_channel_shorts_list). Optional inputs: channelId, handle, sortBy, cursor and includeExtras. Returns a list (use cursor when paginated). Pass channelId (UC…) or handle (e.g. "@mkbhd"). sortBy is latest or popular.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "youtube_channel_videos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor returned by a previous response.
handleNoOptional YouTube channel handle for the request.
sortByNoOptional sort order for the returned YouTube videos.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
channelIdNoOptional YouTube channel id for the request.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
includeExtrasNoOptional flag to include richer per-video metadata when available.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds only the return shape ('Returns a list') and the pagination convention ('use cursor when paginated'), which is genuinely useful but thin — no notes on result limits, rate limiting, or what happens when both channelId and handle are supplied.

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 short sentences, zero filler, with the sibling exclusion and the primary key-selection rule placed before the optional-input enumeration. Nothing needs to be re-read to act on it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter read tool with no output schema, the description covers the domain-relevant parameters (channelId, handle, sortBy, cursor, includeExtras) well enough to call correctly. The three protocol/meta parameters (context, llm_model, conversation_id) are left entirely to their schema text, including the conversation_id handshake, which is a small gap but not one that would cause a wrong call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: the channelId format ('UC…'), a concrete handle example ('@mkbhd'), and the sortBy value semantics (latest vs popular). Those format hints are not in the schema text, which just calls them 'optional ... id' and 'sort order'.

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

Purpose5/5

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

The description names a specific verb and resource ('List long-form videos from a YouTube channel') and immediately distinguishes the scope from the Shorts sibling, so an agent can tell the two apart without opening either schema. The parenthetical exclusion is front-loaded rather than buried.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not rule ('not Shorts — use `youtube_channel_shorts_list`') naming the correct alternative, plus concrete selection guidance between the two lookup keys (channelId as UC… or handle as @mkbhd). That is more than implied usage; the routing decision is stated.

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

Deploy Server

Other Tools