Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_subscribe

Destructive

Subscribes the authenticated YouTube account to a specified channel using its channel ID, and requires explicit confirmation before making the change.

Instructions

Subscribe the authenticated account to a channel.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channelId": "<channelId>"
    },
    "name": "youtube_subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to perform this write; set it only after the user approved the action.
channelIdYesChannel ID (UC...) to subscribe to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / channelId / description
      Added value: +"Channel ID (UC...) to subscribe to."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to perform this write; set it only after the user approved the action."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations mark this destructiveHint=true, but the description adds nothing beyond the tool name: it does not say the action requires explicit user approval, that confirm must be true, or whether subscribing is idempotent. The only behavioral cue (the confirm gate) lives entirely in the schema property text, not the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler. It is efficient but underspecified rather than tight — brevity here comes at the cost of the gating behavior.

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

Completeness2/5

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

For a destructive-flagged write with a mandatory confirmation parameter and no preflight sibling in the toolset, the description should at minimum flag the approval requirement and the absence of a dry-run path. It says none of this, leaving the agent to discover gating from the schema alone.

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%: both channelId (UC... format) and the confirm approval gate are documented inline. The description contributes no additional parameter meaning, which is the expected baseline when the schema is complete.

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?

States a specific verb ('Subscribe') and resource ('channel') against a named actor ('the authenticated account'). It is separable from youtube_unsubscribe and youtube_list_subscriptions by name and verb, though the description itself never references those siblings.

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?

No when-to-use or when-not guidance, no prerequisites, and no mention of the user-approval flow. An agent reading only the description would not know this write is gated behind a confirm flag or that a sibling exists for undoing it.

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

Deploy Server

Other Tools