Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_channel_shorts

Retrieve a YouTube channel's Shorts tab as structured data, including video IDs, titles, URLs, thumbnails, view counts, and pagination tokens to fetch additional pages.

Instructions

Retrieve the shorts tab for a YouTube channel. Returns one page of Shorts from a YouTube channel's Shorts tab. id accepts a channel id, @handle, /c or /user path, or a full channel URL. Each short has its position within this page, video id, title, URL, thumbnail and view count text. Pass continuation_token from the response to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
idYesChannel ID, @handle, /c path, /user path, or full YouTube channel URL
continuation_tokenNoOpaque pagination token returned by the previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.16
    • addedInput schema / properties / continuation_token
      Added value: +{
+  "description": "Opaque pagination token returned by the previous response",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose useful behavior: it returns one page, enumerates the per-short fields (position, video id, title, URL, thumbnail, view count), and explains the continuation-token pagination loop. It doesn't mention auth or rate limits, but for a public read this is good coverage.

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?

Front-loaded with the core action, and the pagination cue comes last where it belongs. The first two sentences overlap ('Retrieve the shorts tab' / 'Returns one page of Shorts from ... Shorts tab'), a minor redundancy, but otherwise tight.

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 a two-param, read-only list tool with no annotations and no output schema, the description supplies enough: what a page contains, the id format options, and how to paginate. Little important context is missing beyond auth/rate-limit details that are unlikely to matter here.

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 coverage is 100%, so the meaning of both params is already in the schema. The description restates the `id` formats and pagination token but adds no syntax or edge-case detail beyond what the schema's property descriptions already say. Baseline 3 applies.

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?

States a specific verb and resource ('Retrieve the shorts tab for a YouTube channel') and the scope 'one page of Shorts from the channel's Shorts tab'. The shorts-specific framing clearly distinguishes it from the channel videos/playlists siblings without needing to name them.

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?

Usage is implied by the description of pagination ('pass continuation_token from the response to fetch the next page') and the accepted id formats, but it never states when to use this vs youtube_channel_videos or other channel tools, nor any exclusions or prerequisites.

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