Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_list_subscriptions

Read-only

Retrieve subscriptions for the authenticated YouTube account with pagination, optionally adding subscriber counts, video counts, and last upload times per channel.

Instructions

List subscriptions for the authenticated account, with pagination. details: true adds subscriberCount, videoCount and lastUploadAt per channel and costs about 1 extra quota unit per returned channel.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_list_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsNoAdd subscriberCount, videoCount and lastUploadAt per channel. Costs roughly 1 extra quota unit per returned channel plus 1 per 50 channels.
pageTokenNoPage token from the nextPageToken of a previous response, to fetch the next page.
maxResultsNoMaximum number of items to return, 1-50; omit to use the tool default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / maxResults / description
      Added value: +"Maximum number of items to return, 1-50; omit to use the tool default."
    • addedInput schema / properties / pageToken / description
      Added value: +"Page token from the nextPageToken of a previous response, to fetch the next page."
  2. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / details
      Added value: +{
+  "description": "Add subscriberCount, videoCount and lastUploadAt per channel. Costs roughly 1 extra quota unit per returned channel plus 1 per 50 channels.",
+  "type": "boolean"
+}
    • addedInput schema / properties / pageToken
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint already declares the safety profile, and the description adds genuinely useful context beyond it: pagination exists, and enabling details incurs roughly one extra quota unit per returned channel. That quota disclosure is real behavioral value an agent cannot get from annotations. It stops short of describing error or empty-result behavior.

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?

Two short sentences, front-loaded with the core purpose, with no filler. The second sentence partially duplicates the schema's details parameter description, which is the only wasted space.

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

Completeness4/5

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

There is no output schema, so the description should ideally sketch the returned shape; it names the extra fields details adds but not the base fields of a subscription entry (channel id/title). Given only three optional parameters and a read-only annotation, this is close to sufficient.

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%, so all three parameters are already documented — and the schema's details text is actually richer ("plus 1 per 50 channels"). The description restates the details cost at a lower level of precision and says nothing about pageToken or maxResults, so it adds no meaning beyond the schema. Baseline 3.

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 states a specific verb and resource ("List subscriptions for the authenticated account") plus the pagination behavior, which cleanly separates it from youtube_subscribe / youtube_unsubscribe. It does not explicitly name those siblings, but the read-only listing scope is unambiguous.

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?

Usage context is only implied: the agent can infer this is the read path for the account's subscriptions, and the details note hints at a cost/benefit tradeoff. There is no explicit statement of when to prefer this over youtube_get_channel or youtube_search, and no prerequisites (e.g., auth required) are stated.

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