Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Twitter community tweets

twitter_community_tweets_list
Read-onlyIdempotent

Fetches tweets from an X community by URL or numeric ID, with pagination via cursor for monitoring or research.

Instructions

List tweets from an X community by community id or URL. Requires url. 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": {
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "twitter_community_tweets_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Community permalink or numeric id.
cursorNoOpaque pagination cursor returned by a previous response.
sortByNoCommunity tweet sort order. Defaults to `relevance`.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, open-world read, so the safety profile is fully covered. The description only adds the pagination hint about using a cursor; it does not mention that conversation_id must be awaited before parallel calls, the rate-limit/auth situation, or the shape of the returned list. No contradiction with annotations.

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: purpose first, then the required parameter and the return shape, with zero filler. It is efficient, though slightly redundant with the schema on url and lacking in depth given the six-parameter surface.

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 no output schema, the description is adequate but thin: it says a list comes back without describing item fields, result caps, or empty-result behavior. The pagination mention is helpful, but the analytics-only parameters (context, llm_model, conversation_id) receive no coverage in the description and the richest guidance lives 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 every one of the six parameters (url, cursor, sortBy, context, llm_model, conversation_id) is already documented in the schema, and the description correctly restates the mandatory url plus the cursor use. It adds no additional meaning on sortBy defaults, acceptable URL forms, or how context/llm_model are supposed to be filled, so the baseline 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?

The description states a specific verb and resource ("List tweets from an X community") and identifies the required selector (community id or URL), so an agent can act on it immediately. It doesn't differentiate itself from close siblings such as twitter_community_search_list or twitter_list_tweets_list, which remain distinguishable only by name.

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 implied rather than stated: use it when you want a community's tweet feed and you have a community id or permalink. There is no explicit when-not to use it, no pointer to twitter_community_search_list for keyword searches, and no statement about what sortBy=relevance versus recency is meant for.

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