Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_unsubscribe

Destructive

Removes a subscription from the authenticated YouTube account using its subscription ID, with confirmation required before the change is made.

Instructions

Remove an authenticated-account subscription.

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": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "youtube_unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to perform this write; set it only after the user approved the action.
subscriptionIdYesSubscription ID (not the channel ID), from youtube_list_subscriptions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to perform this write; set it only after the user approved the action."
    • addedInput schema / properties / subscriptionId / description
      Added value: +"Subscription ID (not the channel ID), from youtube_list_subscriptions."
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotation 'destructiveHint: true' covers the primary behavioral concern (mutation). The description adds the scope of 'authenticated-account' which is helpful but doesn't add deep behavioral context beyond the annotations.

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 single sentence is maximally concise, stating exactly what the function does without any fluff or unnecessary qualification.

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 action, the definition is critically incomplete. It fails to guide the user on how to obtain the required 'subscriptionId', leading to likely invocation failures.

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%, meaning the input schema fully describes the parameters. The description provides no additional semantic meaning or explanation for the 'subscriptionId' or 'confirm' parameters.

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 purpose is clear: it uses the verb 'Remove' and targets the resource 'subscription'. It is immediately distinguishable from the sibling 'youtube_subscribe' because of the action, though it could benefit from explicitly naming 'YouTube'.

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?

The description provides zero guidance on when or how to use the tool relative to alternatives. It does not mention that the subscriptionId must first be retrieved using 'youtube_list_subscriptions', which is crucial for agent logic.

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