Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List YouTube channel community posts

youtube_channel_communityPosts_list
Read-onlyIdempotent

Lists a YouTube channel's community posts from its Posts tab, newest first, and supports cursor pagination so you can review or monitor channel updates. Provide a channel ID or handle.

Instructions

List the community posts on a YouTube channel's Posts tab, newest first. Optional inputs: channelId, handle 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_communityPosts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor returned by a previous response.
handleNoYouTube channel handle whose posts should be listed, with or without a leading @.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
channelIdNoYouTube channel id whose posts should be listed.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds two genuinely new behavioral facts — results are newest-first and pagination is cursor-driven — but says nothing about rate limits, auth, or result size.

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?

Two short sentences, front-loaded with the purpose and ordering before the parameter note. No filler, no restatement of the title, and the pagination hint is attached where it is useful.

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 read-only list tool with full schema coverage and rich annotations, most of the burden is already carried elsewhere, and the description does say it returns a list and how to paginate. The remaining gap is the identifier selection rule (channelId vs handle) and any note on result volume, which an agent needs to call it correctly on the first try.

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 all six parameters are already documented in the schema, including the handle's leading-@ tolerance and the cursor's opacity. The description only restates that these three are optional and adds no semantics beyond the schema; the two required meta-parameters (context, llm_model) are not mentioned at all.

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 (list community posts) plus the surface it targets (a channel's Posts tab) and the ordering (newest first), which is enough to distinguish it from the video/shorts list siblings. It does not explicitly route away from youtube_community_post_get, so it stops short of full sibling differentiation.

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 description frames channelId, handle and cursor as "optional inputs", which implies the tool is used per-channel but never says that at least one channel identifier must be supplied or how to choose between channelId and handle. There is no when-not guidance or named alternative (e.g., the single-post getter), so usage is only implied.

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