Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

youtube_search

Read-onlyIdempotent

Search YouTube for videos, channels, or playlists by query, with filters for type, order, region, date, and result count. Use it to find relevant content for research and automation.

Instructions

Search YouTube for videos, channels, or playlists.

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>",
      "query": "<query>"
    },
    "name": "youtube_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNovideo, channel, or playlist (default: video)
orderNorelevance, date, rating, viewCount, title
queryYes
api_keyYes
channel_idNo
page_tokenNo
max_resultsNo
region_codeNo
published_afterNoRFC 3339 datetime, e.g. 2024-01-01T00:00:00Z

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the set of searchable resource types, and says nothing about quota consumption, API key requirements, or that paging via page_token is needed to go beyond a single result page.

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?

A single front-loaded sentence with no filler — every word earns its place. It is however under-sized for a 9-parameter search tool, bordering on under-specification rather than true economy.

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?

With 9 parameters, 6 undocumented by schema, no output schema, and pagination available via page_token, the description leaves an agent without enough information to call the tool correctly — it should at least mention required auth and how to page/size results.

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 only 33%: query, api_key, channel_id, page_token, max_results, and region_code carry no schema descriptions at all. The description covers only the 'type' dimension (videos/channels/playlists) and leaves half a dozen parameters unexplained, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Search YouTube for videos, channels, or playlists'), which is clear enough for an agent to understand the operation. It does not, however, distinguish itself from siblings like youtube_get_video, youtube_get_channel, or youtube_list_playlists, so the boundary between searching and fetching by ID is left implicit.

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

Usage Guidelines3/5

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

The verb 'search' implies keyword-driven discovery, but the description never states when to use this versus youtube_get_video (ID lookup) or youtube_list_playlists (enumeration). No prerequisites, no mention of the required YouTube API key, no guidance on pagination or result caps.

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