Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

List Subscriptions

youtube_list_subscriptions
Read-onlyIdempotent

Retrieve your YouTube subscriptions with sorting by relevance, unread activity, or alphabetically. Supports pagination and output in markdown or JSON format.

Instructions

List all channels that the authenticated user is subscribed to, using the YouTube Data API v3 subscriptions.list endpoint with mine:true.

Args:

  • order — Sort order for the returned list. One of:

    • relevance (default) — YouTube's relevance ranking.

    • unread — Channels with new activity appear first.

    • alphabetical — Alphabetical by channel title.

  • maxResults — Number of subscriptions to return per page (1–50, default 25).

  • pageToken — Pagination cursor. Pass the nextPageToken from a previous response to retrieve the next page. Optional.

  • response_format"markdown" (default, human-readable summary) or "json" (full structured data).

Returns (JSON shape):

{
  "nextPageToken": "string | null",
  "pageInfo": { "totalResults": 142, "resultsPerPage": 25 },
  "items": [
    {
      "id": "subscription-resource-id",
      "snippet": {
        "publishedAt": "2021-03-10T08:00:00Z",
        "title": "Channel Title",
        "description": "Channel description...",
        "resourceId": { "kind": "youtube#channel", "channelId": "UCxxxxxx" },
        "thumbnails": { "default": { "url": "https://..." } }
      },
      "contentDetails": {
        "totalItemCount": 312,
        "newItemCount": 5,
        "activityType": "all"
      }
    }
  ]
}

Examples:

  1. List first 25 subscriptions alphabetically: { "order": "alphabetical" }

  2. Find channels with new videos: { "order": "unread", "maxResults": 10 }

  3. Paginate to the next page: { "pageToken": "<nextPageToken from previous call>" }

Common Errors:

  • 401 / 403 authError — Credentials missing or expired; re-run npm run auth.

  • 403 forbidden — The authenticated account does not have permission to list its own subscriptions; check scopes include https://www.googleapis.com/auth/youtube.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoSort order: "relevance" (default), "unread" (new activity first), or "alphabetical".relevance
maxResultsNoNumber of subscriptions to return per page (1–50). Default: 25.
pageTokenNoPagination cursor. Pass the nextPageToken from a previous response to get the next page.
response_formatNoOutput format: "markdown" (default, human-readable) or "json" (full structured data).markdown
Behavior4/5

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

Annotations already indicate read-only, idempotent, and open-world behavior. The description adds valuable context about the API endpoint, common errors (auth errors, permissions), and pagination, enhancing transparency beyond annotations.

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 well-structured with sections (Args, Returns, Examples, Common Errors), front-loaded with the core purpose, and every sentence is meaningful. No redundant or wasteful content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description provides a complete JSON return shape. It covers all parameters, pagination, error handling, and examples. The tool's complexity is fully addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions, but the description adds extra value by explaining effects of each parameter (e.g., order meanings), providing examples, and detailing return shape. This goes beyond the schema's basic descriptions.

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 clearly states the tool lists all channels the authenticated user is subscribed to, using a specific verb and resource ("List all channels"). It distinguishes from sibling tools, as no other tool lists subscriptions.

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

Usage Guidelines4/5

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

The description provides clear context on how to use the tool (e.g., pagination, parameter examples) but does not explicitly state when to use this tool vs alternatives. However, the purpose is unique among siblings, so the lack of exclusions is acceptable.

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/tuitamogamer-gpt/youtube-mcp-server'

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