Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

youtube_list_playlists

Read-onlyIdempotent

Lists playlists for a specified YouTube channel using its channel ID and API key, with optional pagination and result limits.

Instructions

List playlists belonging to a YouTube channel.

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": {
      "api_key": "<api_key>",
      "channel_id": "<channel_id>"
    },
    "name": "youtube_list_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYes
channel_idYes
page_tokenNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds nothing beyond purpose—it does not mention pagination via page_token, rate limits, API key requirements, or result ordering—so it contributes very little behavioral context.

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

Conciseness4/5

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

The single sentence is front-loaded and free of waste, with the core action and scope stated immediately. Its brevity is efficient, though it leans toward under-specification rather than crisp completeness.

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?

This is a paginated list operation with four undocumented parameters and no output schema. The agent cannot learn from the description how authentication, paging, or result limits work, which are necessary to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters. The description only implies channel_id by referencing a channel; it says nothing about api_key, page_token, or max_results, so it fails to compensate for the undocumented schema.

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 sentence names a specific verb (List) and resource (playlists) scoped to a YouTube channel, which is clear on its own. It implicitly distinguishes from youtube_list_playlist_items, but never names that sibling or any other, so it falls short of full differentiation.

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 guidance on when to use this instead of youtube_list_playlist_items, youtube_get_channel, or youtube_search, and no prerequisites or exclusions are stated. The agent must infer the use case purely from the tool name.

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