Skip to main content
Glama

search_videos

Search YouTube videos, channels, or playlists by query and filter results by type, order, region, and publish date.

Instructions

Search videos/channels/playlists — port of youtube-mcp search_videos.

Layer: YouTube Data API (key required). Quota: 100 units.
Returns {success, query, total_results, next_page_token, results[]}.

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
rawNo
orderNorelevance
queryYes
max_resultsNo
region_codeNo
search_typeNovideo
published_afterNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that a YouTube Data API key is required and that each call costs 100 quota units, which is genuinely useful cost/auth context. It omits error behavior, pagination mechanics despite exposing `next_page_token`, and whether results are cached or live.

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 description is short and front-loads the core action, then layers quota and return shape. The provenance line ("port of youtube-mcp search_videos") adds little for an invoking agent, and the fragmented line-break layout is slightly harder to parse than a single flowing statement.

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?

An output schema exists, so the return-shape note is a bonus rather than a necessity, and the auth/quota disclosure covers the operational side. The serious gap is the 7 undocumented parameters layered on a 0%-coverage schema, which leaves the definition incomplete for anything beyond a bare `query` call.

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

Parameters4/5

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

Schema description coverage is 0% across all 7 parameters, so the description must compensate, and it largely does not: `order`, `max_results`, `region_code`, `published_after`, `search_type`, and `raw` are never explained. Only the query/search scope is implied by the opening phrase, leaving the agent to guess at accepted values and format (e.g., ISO-8601 for dates, enum values for `order`).

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 set ("Search videos/channels/playlists") and identifies the upstream implementation it ports. The scope is clear, but it blurs the boundary with the sibling `search_channels` by claiming to also search channels, leaving the agent unsure which tool wins for channel lookups.

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 when-to-use or when-not-to-use guidance, and no sibling (`youtube_search`, `search_channels`, `youtube_get_channel_videos`) is named as an alternative. The only routing-adjacent information is the quota cost, which informs budgeting but not tool selection.

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