Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_reset_consumption_data

Destructive

Deletes a selected profile's local consumption data—curation policy, candidates, and queues—after explicit approval.

Instructions

Delete selected-profile local curation policy, candidates, and queues.

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_reset_consumption_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to delete the local consumption data; set it only after the user approved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to delete the local consumption data; set it only after the user approved."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description adds genuine value beyond that by enumerating precisely what is destroyed (policy, candidates, queues) and clarifying the data is "local". It stops short of stating irreversibility or whether a re-save can restore state, and the phrase "local curation" is not defined.

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?

A single sentence with the destructive verb front-loaded and zero filler; every word (selected-profile, local, the three resource types) carries information.

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

Completeness3/5

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

For an irreversible, annotation-flagged destructive tool with no output schema and no preflight sibling, the description should say whether the deletion is recoverable and what state remains afterward. It names the targets but leaves the agent guessing about consequences of an unrecoverable action.

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?

There is a single parameter and schema description coverage is 100%, with the confirm flag's approval semantics fully spelled out in the schema. The description adds nothing about confirm, so the baseline 3 applies — the schema does all the work.

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?

Uses a specific verb ("Delete") plus an enumerated resource set ("local curation policy, candidates, and queues") scoped to the selected profile, so an agent knows exactly what is removed. It does not, however, name or rule out the sibling curation tools (youtube_save_curation_policy, youtube_save_curation_candidate, youtube_propose_consumption_queue) that operate on the same data.

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 never states when to call this versus the sibling curation tools, nor any prerequisite such as an active selected profile or prior user approval. It omits that every other destructive sibling (delete_playlist, delete_comment, etc.) has a *_preflight_ counterpart, while this one does not, leaving the agent without routing guidance.

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