Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search inside a YouTube channel

youtube_channel_search_list
Read-onlyIdempotent

Search one YouTube channel by handle for videos, Shorts, live streams, and playlists matching a keyword, so you can locate relevant content within that channel.

Instructions

Search one YouTube channel's videos, Shorts, live streams and playlists by keyword (for all of YouTube, use youtube_search_list). Requires handle and query. Returns a list (use cursor when paginated).

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": {
      "handle": "<handle>",
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "youtube_channel_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Text to search for in the channel's uploads.
cursorNoOpaque pagination cursor returned by a previous response.
handleYesRequired. YouTube channel handle to search inside, with or without a leading @.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.
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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that results come back as a list and that pagination is cursor-based, which is useful but largely restates what the cursor parameter's schema description already says. No further context on result volume, ranking, or empty-result behavior.

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 short sentences with zero filler: scope and content types first, the alternative second, required inputs and return shape last. Every clause carries information the agent needs to select and call the tool.

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?

There is no output schema, and the description compensates by stating that the result is a list with cursor pagination. Combined with full schema coverage and clear annotations, an agent has enough to call it correctly; only matching/ranking semantics and result size remain unstated, which are minor for a read-only search.

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 every parameter including handle, query, cursor and the context/llm_model/conversation_id bookkeeping fields is already documented. The description only repeats that handle and query are required, adding no format or matching semantics (e.g., whether query matches titles only or full text). 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?

States a specific verb (search) and a precise scope (one YouTube channel), enumerates the content types covered (videos, Shorts, live streams, playlists), and names the sibling it is not (youtube_search_list for all of YouTube). An agent can distinguish it from youtube_channel_videos_list and youtube_search_list without opening a 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?

Explicitly routes the agent to youtube_search_list when the scope is all of YouTube, and states the two required inputs. It does not say when to prefer plain listing siblings like youtube_channel_videos_list or shorts_list over a keyword search, so one edge remains for inference.

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