Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_unsubscribe_many

Destructive

Preview removal of up to 100 YouTube subscriptions by validating account ownership and listing each channel title before deletion, with approximate quota cost of 50 units per removal.

Instructions

Preview removing up to 100 subscriptions of the authenticated account: verifies each belongs to the account and lists every channel title to be removed, with approximate quota (50 units per removal).

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": {
      "subscriptionIds": "<subscriptionIds>"
    },
    "name": "youtube_preflight_unsubscribe_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscriptionIdsYesSubscription IDs to remove, 1-100, from youtube_list_subscriptions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / subscriptionIds / description
      Added value: +"Subscription IDs to remove, 1-100, from youtube_list_subscriptions."
  2. Addedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds real behavioral context beyond the destructiveHint annotation: quota cost (~50 units per removal), ownership verification per channel, and confirmation that all channel titles are returned. It does not explain why a non-mutating preview carries destructiveHint=true, nor whether a follow-up execute call is required, which is the remaining gap.

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?

One dense sentence with the action and limit front-loaded, followed by verification behavior and cost. Every clause carries information an agent needs; nothing is padding.

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?

For a single-parameter preflight tool with no output schema, it covers the essentials: what is checked, what is returned (channel titles), the scale limit, and the quota price. What is missing is how the result should feed into the actual removal call and whether any token/confirmation is produced.

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 coverage is 100% for the single subscriptionIds parameter, which already documents the 1-100 range and its source (youtube_list_subscriptions). The description only restates the cap ('up to 100') and adds ownership checking, so the schema does the substantive work — baseline 3.

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?

States a specific verb (preview removing), the exact resource (subscriptions of the authenticated account) and the scope cap (up to 100). The word 'Preview' cleanly separates it from the execute siblings youtube_unsubscribe and youtube_unsubscribe_many without needing to open any schema.

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 'Preview' framing makes the intended use — a dry run before the destructive removal — clear, and it implies IDs come from a listing step. However it never explicitly names youtube_unsubscribe_many as the follow-up action or states any when-not condition, so the routing is implied rather than spelled out.

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