Skip to main content
Glama
fetchtranscript-mcp

fetchtranscript-mcp

Official

list_channel_videos

Retrieve videos from a YouTube channel by ID or handle, with pagination controls and an optional switch to include Shorts.

Instructions

List videos from a YouTube channel.

Args: channel_id: YouTube channel ID (UCxxxxxx format) or handle (@username) limit: Number of videos to return (default 10, max 100) offset: Number of videos to skip for pagination (default 0) include_shorts: Whether to include YouTube Shorts (default false)

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": {
      "channel_id": "<channel_id>"
    },
    "name": "list_channel_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
channel_idYes
include_shortsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the accepted identifier formats (UCxxxxxx or @username) and the pagination mechanism, which is genuinely useful. However, it says nothing about ordering of results, quota/rate-limit behavior, or whether the call requires an API key, and it omits any note that Shorts are excluded by default—a behaviorally significant default that only appears in the arg list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-line purpose is front-loaded, followed by a compact parameter list where every line adds information. Structure is clean and there is no filler, though the arg block reads like schema restatement for the defaulted fields.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and all four parameters are documented. What is missing is behavioral and selection context—result ordering, whether Shorts filtering changes pagination, and why an agent would pick this over search_videos—which matters for a channel-enumeration tool with zero annotation coverage.

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 description coverage is 0%, so the description must compensate, and it largely does: it documents all four parameters with accepted formats, defaults, and the 100-video ceiling that the schema does not express. It stops short of explaining offset/limit interaction beyond the bare definitions, but the added meaning is substantial.

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?

The description states a specific verb and resource ("List videos from a YouTube channel"), so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling search_videos, which also returns video lists, leaving the boundary between listing and searching implicit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of which sibling to prefer for keyword-based retrieval versus channel enumeration. Usage is only weakly implied by the phrase "from a YouTube channel".

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