Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_unsubscribe_many

Destructive

Remove 1-100 approved YouTube subscriptions in bulk after preview approval, reporting each as removed, already gone, failed, or unknown and stopping early if quota runs out.

Instructions

Remove the approved subscriptions one by one and report each as removed, already_gone, failed (definitively rejected) or unknown (outcome uncertain after a server or network error: reconcile with youtube_list_subscriptions before retrying). Stops early (with a partial report) if YouTube quota runs out. Approve with youtube_approve first, then call with confirm: true.

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>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_unsubscribe_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
approvalIdYesApproval ID from the youtube_preflight_unsubscribe_many preview, after approving it with youtube_approve.
subscriptionIdsYesSubscription IDs to remove, 1-100, from youtube_list_subscriptions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_unsubscribe_many preview, after approving it with youtube_approve."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to execute; set it only after youtube_approve approved this exact preview."
    • addedInput schema / properties / subscriptionIds / description
      Added value: +"Subscription IDs to remove, 1-100, from youtube_list_subscriptions."
  2. Addedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply destructiveHint=true, so the description carries most of the burden and does so well: per-item outcome taxonomy (removed/already_gone/failed/unknown), the distinction between definitive rejection and uncertain server/network failure, and early termination with a partial report when quota is exhausted. This is exactly the operational context a batch destructive tool needs.

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?

Three tightly packed sentences, front-loaded with the action and outcome model, then the failure mode, then the approval prerequisite. No filler or restatement of the tool name.

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?

With no output schema, the description does the work of explaining the return report and its partial character, and it covers quota and uncertain-outcome handling. Minor omissions: it never mentions the youtube_preflight_unsubscribe_many preview step (left to the schema) and doesn't say whether iteration continues after a failed item or whether removals are reversible.

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% and all three parameters are documented in the schema, including the confirm and approvalId contract. The description's mention of confirm: true and 'approved subscriptions' mostly restates that contract rather than adding syntax or edge-case semantics (e.g. what happens if confirm is false). Baseline 3 is appropriate.

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?

Names a specific verb and resource ('Remove the ... subscriptions') plus the batch scope ('one by one'), and immediately enumerates the four outcome states. This clearly distinguishes it from the single-item sibling youtube_unsubscribe without the agent needing to open either schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite chain ('Approve with youtube_approve first, then call with confirm: true') and explicit retry guidance for the uncertain case ('reconcile with youtube_list_subscriptions before retrying'). Names the alternative tool and the condition that selects 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