Skip to main content
Glama

get_channel_shorts

Retrieve recent YouTube Shorts from a specific channel URL to monitor short-form video content. Specify a limit to control the number of videos returned.

Instructions

List recent Shorts from a specific YouTube channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_urlYesYouTube channel URL (e.g. https://www.youtube.com/@ChannelName)
limitNoMax shorts to return (default 15)

Implementation Reference

  • The tool registration and handler implementation for get_channel_shorts. It validates the URL, checks dependencies, and calls fetchShortsFromChannel to retrieve the data.
    server.tool(
      'get_channel_shorts',
      'List recent Shorts from a specific YouTube channel.',
      {
        channel_url: z.string().url().describe('YouTube channel URL (e.g. https://www.youtube.com/@ChannelName)'),
        limit: z.number().min(1).max(50).default(15).describe('Max shorts to return (default 15)'),
      },
      async ({ channel_url, limit }) => {
        const urlErr = validateYouTubeUrl(channel_url);
        if (urlErr) return errorResult(urlErr);
        const depErr = checkDeps();
        if (depErr) return errorResult(depErr);
    
        try {
          const shorts = await fetchShortsFromChannel(channel_url, limit);
          return textResult({ channel: channel_url, count: shorts.length, shorts });
        } catch (err) {
          return errorResult(`Error: ${err instanceof Error ? err.message : String(err)}`);
        }
      }
    );
  • The fetchShortsFromChannel helper function used by the get_channel_shorts tool to perform the actual data fetching.
    async function fetchShortsFromChannel(channelUrl: string, limit: number) {
      const url = `${stripChannelSuffix(channelUrl)}/shorts`;
      const result = await fetchFeed(url, limit);
      return (result.entries || []).map(pickVideoFields);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'recent' (temporal scope), but lacks critical behavioral details: return format/schema, pagination behavior, authentication requirements, rate limits, or error handling (e.g., private channels).

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?

Single efficient sentence with zero waste. Front-loaded with action verb 'List', followed by temporal qualifier 'recent', content type 'Shorts', and target 'specific YouTube channel'. Every word earns its place.

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?

Adequate for a simple 2-parameter tool with complete input schema documentation. However, lacking an output schema, the description omits what data structure is returned (URLs, metadata, etc.), leaving a minor gap in completeness.

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?

With 100% schema description coverage, the schema fully documents both parameters (channel_url format and limit constraints). The description adds minimal semantic value beyond the schema, meeting the baseline expectation when structured documentation is complete.

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?

The description uses specific verb 'List' with clear resource 'Shorts' and scope 'specific YouTube channel'. It effectively distinguishes from siblings: 'Shorts' differentiates from get_channel_videos (regular videos), and 'specific channel' differentiates from get_subscription_shorts (subscriptions).

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 usage through specificity (Shorts vs regular videos, specific channel vs subscriptions), but lacks explicit when-to-use guidance or explicit comparison to alternatives like get_channel_videos or get_subscription_shorts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ronantakizawa/social-video-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server