Crawlora MCP

youtube_channel_shorts

Read-only

Fetch the first page or later Shorts entries from one YouTube channel's Shorts tab with optional continuation_token pagination. Use youtube_channel_videos for regular uploads or youtube_channel_search to find a channel.

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": {
      "id": "<id>"
    },
    "name": "youtube_channel_shorts"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	YouTube video, playlist, or channel id/handle/URL.
`continuation_token`	No	Pagination token from a previous response.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedInput schema / properties / continuation_token

Added value: +{
+  "description": "Pagination token from a previous response.",
+  "type": "string"
+}

changedInput schema / properties / id / description

Previous value: -"YouTube video id, or channel id/handle/URL depending on the endpoint."New value: +"YouTube video, playlist, or channel id/handle/URL."

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new behavior: it returns only the first page unless continuation_token is supplied. It does not discuss result ordering, page size, or limits, which keeps it below a 5.

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?

Two sentences, zero filler, with the pagination scope front-loaded before the sibling routing guidance.

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 an output schema and annotations present, the description need not explain return values, and it covers scope, pagination, and alternatives. Minor gaps remain around how many entries a page holds and ordering, but nothing that would cause a misinvocation.

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 both parameters are already documented in the schema. The description reinforces that continuation_token drives pagination ('first page or later'), but adds no format or provenance detail beyond 'Pagination token from a previous response.' 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 (fetch) and resource (Shorts entries from one channel's Shorts tab) and scopes the page behavior. It explicitly distinguishes itself from youtube_channel_videos and youtube_channel_search, so an agent can pick it without inspecting schemas.

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?

Names two concrete alternatives and the condition each covers: channel_videos for regular uploads, channel_search for locating a channel. Nothing about when to use this versus siblings is left implicit.

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

All Crawlora MCP tools Inspect

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

Need Help?