Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search YouTube

youtube_search_list
Read-onlyIdempotent

Search YouTube content by free-text keyword to find videos, Shorts, channels, or playlists; apply type, region, duration, upload date, and sort filters for targeted results.

Instructions

Search YouTube videos, channels, and playlists by free-text keyword (not hashtag — use youtube_search_hashtag_list for that). Requires query. Returns a list (use cursor when paginated). Example: {"query":"lofi beats","type":"videos"}. type takes plural values: videos, shorts, 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "youtube_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional content type filter for search results.
queryYesRequired. Search query text for YouTube content.
cursorNoOpaque pagination cursor returned by a previous response.
regionNoOptional ISO 3166-1 country code for localized search results.
sortByNoOptional sort order for search results.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
durationNoOptional duration filter for video results. Applies to videos, not shorts.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
uploadDateNoOptional upload date filter for video results.
includeExtrasNoWhen true, returns richer per-video metadata when available. May increase response time.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that results are a list and that pagination uses a cursor, but says nothing about result caps, quotas, or the includeExtras latency tradeoff that the schema mentions.

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 routing constraint is front-loaded and the example is placed before the enum restatement, so the important information comes first. The trailing sentence enumerating plural type values largely duplicates the schema enum and is the only wasted line.

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

Completeness5/5

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

For an 11-parameter search tool with full schema coverage and rich annotations, the description covers purpose, the key sibling distinction, the required query, the pagination mechanism, and a worked example. Remaining filters (region, sortBy, duration, uploadDate, includeExtras) and the conversation_id protocol are already spelled out in the schema.

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 description coverage is 100%, so the baseline is 3 and the schema already documents all 11 parameters. The description's example and its restatement of the type enum ('videos, shorts, channels or playlists') add a usage illustration but no meaning beyond the structured fields.

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 videos, channels, and playlists') and scopes it to free-text keyword search. It explicitly names the sibling it is not (youtube_search_hashtag_list), so an agent can distinguish the two without opening either 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 an explicit when-not rule for the hashtag tool and a concrete example call, which is clear usage context. It does not address other plausible siblings such as youtube_channel_search_list or youtube_shorts_trending_list, so routing guidance is good but not exhaustive.

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