Skip to main content
Glama

Search my videos

youtube_search_videos
Read-onlyIdempotent

Search your connected channel's video library by keyword in titles, tags, and descriptions without consuming YouTube quota. Locate relevant videos for analysis or review.

Instructions

Search the connected channel's own video library (keyword match; uses no YouTube quota).

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": "youtube_search_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to find in titles, tags and descriptions, e.g. 'artificial intelligence'
channel_idNoYouTube channel ID (UC...). Omit to use the default connected channel.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavior beyond that – no YouTube quota is consumed – but says nothing about result ordering, truncation by limit, or what happens when the query matches nothing.

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 compact sentence with the scoping constraint front-loaded and the useful quota note in parentheses. Nothing is wasted, though the parenthetical could have been spent on something an agent cannot get from schema or annotations, such as ordering.

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?

With an output schema present and annotations covering safety, the description only needs to convey scope and cost, which it does. What is missing — result ordering and behavior at the limit boundary — is minor for a read-only search tool.

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 67% and the schema already explains query semantics (titles, tags, descriptions) and the default-channel behavior for channel_id. The description adds no meaning beyond that; limit remains undocumented in the prose, which the schema's min/max only partly compensates for.

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 (search) and resource (connected channel's own video library) plus the match mode (keyword). It implicitly separates itself from youtube_list_videos by being a keyword search rather than an enumeration, but never names that sibling, so an agent must infer the distinction.

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 phrase 'connected channel's own video library' signals when this applies (local search over your own content), and 'uses no YouTube quota' hints it is cheap to call. There is no explicit when-to-use versus youtube_list_videos or youtube_get_video_details, and no stated precondition that a channel must already be connected.

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