Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List YouTube channel shorts

youtube_channel_shorts_list
Read-onlyIdempotent

Lists Shorts from a YouTube channel, excluding long-form videos, with optional channel ID or handle, sorting by recency or popularity, and cursor-based pagination.

Instructions

List Shorts from a YouTube channel (not long-form videos). Optional inputs: channelId, handle, sortBy and cursor. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "youtube_channel_shorts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor returned by a previous response.
handleNoOptional YouTube channel handle for the request.
sortByNoOptional sort order for the returned YouTube Shorts.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
channelIdNoOptional YouTube channel id for the request.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that results are paginated via cursor and that only Shorts are returned, which is useful, but it says nothing about ordering defaults, result limits, or behavior when the channel is ambiguous or missing.

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?

Two short sentences with the scope constraint front-loaded and no filler. The parameter enumeration largely restates the schema and is the one low-value clause.

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?

For a 7-parameter list tool with no output schema, stating that it returns a list and how pagination works is helpful. However, the two required bookkeeping parameters (context, llm_model) and the channel-identification requirement go unmentioned in the description, and there is no note on result shape or limits.

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 is already documented, including the sortBy enum and the cursor's opaque-pagination semantics. The description merely lists parameter names ('Optional inputs: channelId, handle, sortBy and cursor') without adding syntax, defaults, or exclusivity rules, so the baseline of 3 applies.

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 (List) and resource (Shorts from a YouTube channel) and explicitly narrows the scope with '(not long-form videos)', which implicitly separates it from youtube_channel_videos_list. It stops short of naming that sibling, so an agent still has to infer the routing.

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?

Usage is only implied by the purpose statement; there is no explicit when-to-use, when-not, or named alternative. It also omits the practically important point that a channel must be identified via channelId or handle, so nothing tells the agent what to do when neither is supplied.

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