Skip to main content
Glama
Sign In

YouTube Transcript AI

by ai.youtube-transcript
OverviewDiscussionsAdmin

List channel videos

list_channel_videos
Read-only

List the latest videos of a YouTube channel or playlist, with view count and duration. Use it to follow a creator who looks credible, or to cover a playlist. Returns at most 50 videos per call; to go further, call again with offset set to the number of videos already read (the result ends with the offset to use). Reaches up to the first 500 videos.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many videos. Default 20.
offsetNoOptional. How many videos to skip, to read the next page. Use the value given at the end of the previous result. Default 0.
channelYesA channel @handle (e.g. "@RachelsEnglish"), a channel or playlist URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Optional. How many videos to skip, to read the next page. Use the value given at the end of the previous result. Default 0.",
+  "maximum": 499,
+  "minimum": 0,
+  "type": "integer"
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the operational envelope: at most 50 videos per call, an offset-based continuation pattern, and a hard ceiling of the first 500 videos. It also states that the previous result carries the offset to use next, which is real behavioral information an agent needs to page correctly.

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 output is front-loaded with what the tool returns, then the pagination contract, then the limit — a logical order with no duplicated schema facts. The 'creator who looks credible' clause is slightly vague editorializing, but it is short and conveys intent.

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?

With no output schema, the description usefully describes the shape of results (videos with view count and duration, plus a trailing offset). Ordering guarantees ('latest') are implied, and error behavior for an invalid channel or playlist is not addressed, leaving a minor gap.

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 would be 3, but the description adds meaning beyond the schema by explaining that offset equals 'the number of videos already read' and ties it to the value returned at the end of the previous result. Limit's 50 cap and the 500-video overall ceiling are also surfaced in prose.

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 gives a specific verb and resource ('List the latest videos of a YouTube channel or playlist') and adds the returned fields (view count, duration), so an agent knows exactly what it produces. It does not explicitly differentiate itself from close siblings such as latest_from_channels or search_youtube_videos, which keeps it out of the top band.

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?

It supplies positive usage context — 'to follow a creator who looks credible, or to cover a playlist' — which tells the agent when this fits. It stops short of naming alternatives or stating when to prefer another tool, so no exclusion criteria are given.

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

All YouTube Transcript AI 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