Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Twitter communities

twitter_community_search_list
Read-onlyIdempotent

Search X (Twitter) communities by keyword and return a paginated list of matching results; use the cursor to fetch additional pages.

Instructions

Search X communities by keyword. Requires 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "twitter_community_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Search query for X (Twitter) communities.
cursorNoOpaque pagination cursor returned by a previous response.
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 readOnly, idempotent, non-destructive and open-world behavior, so the description's main addition is that it returns a list and that pagination uses a cursor. It omits the notable protocol requirements — a one-sentence goal in context, the exact llm_model identifier, and echoing conversation_id before parallel calls — all of which live only in the schema.

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, front-loaded with the core action and followed by the return/pagination note. "Requires `query`" mildly duplicates the schema's required list, but there is no other waste.

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 five-parameter read tool with no output schema, the description covers purpose and pagination but says nothing about the three required meta-parameters or the conversation_id sequencing rule that governs correct invocation. The schema carries that burden, so the definition is workable but thin on invocation-critical context.

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 schema already explains query, cursor, context, llm_model and conversation_id in detail. The description only restates that query is required and cursor handles pagination, adding no meaning beyond the structured fields; 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?

"Search X communities by keyword" gives a specific verb (search) and resource (X communities), which is enough to separate it from community_get, community_members_list and community_tweets_list. It stops short of naming any sibling explicitly, so the agent must infer the boundary from names alone.

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 by the verb-plus-resource phrasing, and the cursor note hints at the follow-up call pattern for pagination. There is no explicit when-to-use versus community_get or a keyword-vs-ID distinction, and no stated exclusions.

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