Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

Subscribe to a Channel

youtube_subscribe

Subscribe the authenticated user to a YouTube channel by providing the channel ID.

Instructions

Subscribe the authenticated user to a YouTube channel, using the YouTube Data API v3 subscriptions.insert endpoint.

Args:

  • channelId (required) — The YouTube channel ID to subscribe to (e.g., "UCxxxxxx"). This is the channel's resource ID, not a handle or name. You can obtain it from youtube_search (type: channel) or youtube_list_subscriptions.

Returns (JSON shape):

{
  "id": "new-subscription-resource-id",
  "snippet": {
    "publishedAt": "2024-06-03T10:00:00Z",
    "title": "Subscribed Channel Title",
    "description": "Channel description...",
    "resourceId": { "kind": "youtube#channel", "channelId": "UCxxxxxx" },
    "thumbnails": { "default": { "url": "https://..." } }
  },
  "contentDetails": {
    "totalItemCount": 0,
    "newItemCount": 0,
    "activityType": "all"
  }
}

Examples:

  1. Subscribe to a channel: { "channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw" }

Common Errors:

  • 400 subscriptionDuplicate — The authenticated user is already subscribed to this channel.

  • 400 invalidChannelId — The provided channelId does not correspond to an existing channel.

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

  • 403 forbidden — The authenticated account cannot subscribe (e.g., cannot subscribe to own channel, or missing scope https://www.googleapis.com/auth/youtube).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelIdYesThe YouTube channel ID to subscribe to (e.g. "UCxxxxxx"). Obtain from youtube_search or youtube_list_subscriptions.
Behavior5/5

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

Beyond annotations (mutation, not destructive), the description details the return JSON shape, common errors, and authentication requirements. This is extensive and helpful for the agent to understand all behavioral aspects.

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 clear sections (Args, Returns, Examples, Common Errors). It is concise yet comprehensive, with no unnecessary words.

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 includes a full JSON shape. It covers errors, examples, and parameter details. Everything needed for correct invocation is present.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds crucial context: channelId is a resource ID not a handle, and how to obtain it. This exceeds the schema description and fully clarifies the parameter.

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 action ('Subscribe the authenticated user to a YouTube channel') and the endpoint used (youtube#subscriptions.insert). It distinguishes itself from siblings like youtube_unsubscribe and youtube_search by specifying the exact operation.

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 context on how to obtain the channelId (from youtube_search or youtube_list_subscriptions) and lists common errors (duplicate subscription, invalid channelId, auth issues). It doesn't explicitly contrast with alternatives but offers enough guidance for correct usage.

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