Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_propose_consumption_queue

Destructive

Creates a finite local YouTube consumption queue from selected profiles within a set minute budget, so you can plan what to watch without exceeding your available time.

Instructions

Create a finite selected-profile local consumption queue.

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": {
      "minutes": "<minutes>"
    },
    "name": "youtube_propose_consumption_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutesYesTime budget in minutes, greater than 0 and at most 1440.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / minutes / description
      Added value: +"Time budget in minutes, greater than 0 and at most 1440."
  2. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, which is non-obvious for a tool named 'propose/create queue' — yet the description never says what existing state is replaced or cleared. It also omits whether the queue is generated from the stored profile, whether it is persisted, and what the caller receives. The one annotation present raises a question the description does not answer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no padding, but its brevity comes at the cost of clarity — nearly every term is unexplained rather than omitted as redundant.

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 tool that is annotated as destructive and has no output schema, the description should at minimum explain what the queue is built from, what it displaces, and roughly what comes back. None of that is present, leaving the agent unable to predict the side effects of the call.

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 with 100% schema description coverage including bounds (0 < minutes <= 1440), so the schema carries the semantics. The description's word 'finite' vaguely gestures at the time budget but adds no interpretation beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Create' and resource 'consumption queue' are identifiable, but the qualifiers 'finite', 'selected-profile' and 'local' are undefined jargon that an agent cannot resolve from the description alone. It does not distinguish this from the nearby consumption tools such as youtube_consumption_profile or youtube_save_curation_policy.

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?

There is no statement of when this tool should be used, when it should not, or which sibling it replaces or complements. With several consumption-related siblings in the list, the agent is left to guess which one to call.

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