Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_channel_videos

List videos from a YouTube channel's Videos tab using a channel ID, @handle, /c or /user path, or full URL, and page through results with a continuation token.

Instructions

Retrieve the videos tab for a YouTube channel. Lists the videos on a YouTube channel's Videos tab. id accepts a channel id, @handle, /c or /user path, or a full channel URL. Each item has its video id, title, URL, duration, view count, published text, thumbnail, badges and live flag. Pass the returned continuation_token to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
idYesChannel ID, @handle, /c path, /user path, or full YouTube channel URL
continuation_tokenNoPagination token returned by a previous request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description still discloses that this is a retrieval/listing operation, what each returned item contains, and how pagination works via the returned `continuation_token`. It omits details like ordering, page size, or auth requirements, but covers the core behavior needed for a read-only listing tool.

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 description is appropriately sized and front-loads the tool's purpose, then adds accepted identifier formats, return fields, and pagination. The first two sentences are slightly redundant in restating the Videos tab purpose, which keeps it from a 5.

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?

There is no output schema or annotations, so the description carries the burden of explaining returns and pagination; it does this by listing item fields and explaining `continuation_token`. It is largely complete for invocation, though it could mention result ordering or page size.

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 description coverage is 100%, so both `id` and `continuation_token` are already documented. The description reinforces the accepted `id` formats and adds a useful instruction for passing `continuation_token` to fetch the next page, but it largely repeats schema content rather than adding new parameter semantics.

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 names a specific verb ('Retrieve'/'Lists') and resource ('videos tab for a YouTube channel'), so the agent can understand exactly what is fetched. It does not explicitly contrast this with sibling tools such as youtube_channel_shorts or youtube_channel_playlists, which keeps it from a 5.

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

Usage Guidelines3/5

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

The description implies when to use the tool by specifying the channel Videos tab and explaining accepted `id` formats. However, it does not explicitly say when to prefer this over alternatives like youtube_channel_shorts, youtube_channel_playlists, or youtube_video, nor does it state exclusions.

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