Skip to main content
Glama

get_channel_videos

Retrieve recent video uploads from any YouTube channel by providing the channel URL, with configurable limits for efficient content discovery.

Instructions

List recent video uploads from a specific YouTube channel.

Input Schema

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

Implementation Reference

  • The handler function that executes the 'get_channel_videos' tool, fetching videos from the provided channel URL.
    async ({ channel_url, limit }) => {
      const urlErr = validateYouTubeUrl(channel_url);
      if (urlErr) return errorResult(urlErr);
      const depErr = checkDeps();
      if (depErr) return errorResult(depErr);
    
      const url = channel_url.endsWith('/videos') ? channel_url : `${channel_url.replace(/\/$/, '')}/videos`;
      try {
        const result = await fetchFeed(url, limit);
        const videos = (result.entries || []).map(pickVideoFields);
        return textResult({ channel: result.title || channel_url, count: videos.length, videos });
      } catch (err) {
        return errorResult(`Error: ${err instanceof Error ? err.message : String(err)}`);
      }
    }
  • src/index.ts:265-287 (registration)
    Registration of the 'get_channel_videos' tool with its input schema definition.
    server.tool(
      'get_channel_videos',
      'List recent video uploads 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 videos 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);
    
        const url = channel_url.endsWith('/videos') ? channel_url : `${channel_url.replace(/\/$/, '')}/videos`;
        try {
          const result = await fetchFeed(url, limit);
          const videos = (result.entries || []).map(pickVideoFields);
          return textResult({ channel: result.title || channel_url, count: videos.length, videos });
        } catch (err) {
          return errorResult(`Error: ${err instanceof Error ? err.message : String(err)}`);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal context. It does not specify the timeframe for 'recent' uploads, describe the return structure (e.g., metadata fields, pagination), mention rate limits, or indicate authentication requirements.

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?

The description is a single, efficient sentence with no redundant words. It is appropriately front-loaded with the action and resource, making it easy to scan and understand immediately.

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?

For a tool with two well-documented parameters and no output schema, the description is minimally adequate. However, given the absence of annotations and output schema, the description should ideally clarify the return format or data structure to be considered complete.

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%, with both 'channel_url' and 'limit' fully documented in the input schema. The description adds no additional parameter semantics beyond the schema, but given the high coverage, it meets the baseline expectation without penalty.

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 provides a clear verb ('List') and resource ('recent video uploads from a specific YouTube channel'), making the basic function unambiguous. However, it does not explicitly differentiate from the sibling tool 'get_channel_shorts' or clarify what constitutes 'recent'.

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

Usage Guidelines2/5

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

The description offers no guidance on when to select this tool versus alternatives like 'get_channel_shorts' (for Shorts content), 'search_youtube' (for search queries), or 'get_video_info' (for single video details). No prerequisites or conditions are mentioned.

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