Skip to main content
Glama
youtube-playlists-mcp

youtube-playlists-mcp

by kvechkanov

search_videos

Find YouTube videos by search query and return paginated results, while serving identical requests from cache to reduce API quota usage.

Instructions

Search YouTube for videos. EXPENSIVE: quota cost 100 units per uncached call (about 100 searches/day on the default 10,000-unit quota). Identical queries are served from a local cache (24h by default) at 0 units; the response says cached: true. Use sparingly.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text.
pageTokenNonextPageToken from a previous search (a new page costs 100 units).
maxResultsNo1-10 results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well on the biggest risk: cost. It discloses per-call quota consumption, the daily budget implication, 24h local caching of identical queries, and that the response carries a 'cached: true' flag, so an agent can verify a free hit. It omits auth requirements, per-second rate limits, and error/quota-exhaustion behavior, which keeps it out of 5 territory.

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?

Three tight sentences: purpose first, then the expensive-cost warning, then the cache escape hatch and the imperative 'Use sparingly.' Every sentence carries decision-relevant information and the most important constraint (cost) is front-loaded after the one-line purpose.

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

Completeness4/5

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

For a 3-parameter read tool with no annotations and no output schema, the cost and caching profile is the main thing an agent needs and it is covered thoroughly. The remaining gap is the shape of returned results — beyond the cached flag, the description never says what a video record contains, and there is no output schema to fall back on.

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%, so every parameter (query, pageToken, maxResults) is already documented in the schema, including the paging cost note. The description adds no parameter-level meaning beyond that — its cost discussion is call-level, not argument-level — so the baseline 3 applies.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Search YouTube for videos'), which is immediately distinguishable from the playlist-management siblings (list_my_playlists, add_to_playlist, etc.) that perform no search at all. An agent knows exactly what capability this tool exposes before opening the schema.

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

Usage Guidelines4/5

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

It gives explicit usage guidance: 'Use sparingly' backed by a concrete quota math (100 units per uncached call, ~100 searches/day), plus a reuse rule implied by the cache note and the pageToken warning that a new page costs another 100 units. It stops short of naming alternatives for narrowing results (e.g., listing channel/playlist items instead of searching), so it is clear context rather than a full when/when-not decision tree.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.