Skip to main content
Glama

get_subscribed_channels

Retrieve your YouTube channel subscriptions using browser cookies to manage viewing preferences and content discovery.

Instructions

List your subscribed YouTube channels using Chrome cookies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax channels to return (default 30)

Implementation Reference

  • The tool `get_subscribed_channels` is registered and defined as a handler in `src/index.ts`. It uses `fetchFeed` to retrieve data from the YouTube subscriptions feed and returns a list of channels.
    server.tool(
      'get_subscribed_channels',
      'List your subscribed YouTube channels using Chrome cookies.',
      { limit: z.number().min(1).max(100).default(30).describe('Max channels to return (default 30)') },
      async ({ limit }) => {
        const depErr = checkDeps();
        if (depErr) return errorResult(depErr);
    
        try {
          const result = await fetchFeed('https://www.youtube.com/feed/channels', limit);
          const channels = (result.entries || []).map((e) => ({
            channel: e.channel, channel_url: e.channel_url || e.url, title: e.title,
          }));
          return textResult({ count: channels.length, channels });
        } catch (err) {
          return errorResult(`Error: ${err instanceof Error ? err.message : String(err)}`);
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden and successfully discloses the Chrome cookies dependency (critical auth requirement). However, it lacks disclosure of error handling, return format, or what happens when cookies are missing.

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 single sentence is perfectly front-loaded with the action ('List') and contains zero waste—every word ('your', 'subscribed', 'using Chrome cookies') adds essential context about scope and mechanism.

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?

Given the simple single-parameter input (100% schema coverage) but absence of an output schema, the description adequately covers the operation but leaves a gap by not describing what channel data is returned (IDs, names, URLs, etc.).

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% (the 'limit' parameter is fully documented), establishing the baseline score. The description itself does not add parameter semantics, but none are needed given complete schema coverage.

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 provides a specific verb ('List'), clear resource ('subscribed YouTube channels'), and distinguishes from siblings by specifying 'your' subscriptions and the 'Chrome cookies' authentication method—differentiating it from general channel queries like get_channel_videos or search_youtube.

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 scenarios through 'subscribed' and 'Chrome cookies' (suggesting personal account access), but provides no explicit guidance on when to use this versus alternatives like get_youtube_feed or prerequisites for Chrome setup.

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