Twitter241 MCP Server

get_community_tweets

Retrieve tweets from a specific Twitter community by ID. Filter by search type (default or media) and rank by relevance, recency, or likes.

Instructions

Get Community Tweets by Community ID

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": {
      "communityId": "<communityId>",
      "searchType": "<searchType>"
    },
    "name": "get_community_tweets"
  }
}

Input Schema

Name	Required	Description
`count`	No	Example value: 20
`cursor`	No	Example value:
`searchType`	Yes	Default or Media
`communityId`	Yes	Example value: 1601841656147345410
`rankingMode`	No	Relevance or Recency or Likes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but it does not mention pagination behavior, sorting defaults, required authentication, rate limits, or what data is returned. This is minimal disclosure at best.

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?

The description is a single, front-loaded sentence with no filler words. It is appropriately concise for the limited information it conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and absence of an output schema, the description should compensate by explaining the tool's behavior in more detail. It does not clarify how searchType and rankingMode affect results, how cursor-based pagination works, or what the returned data looks like, leaving the tool under-specified for an agent.

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?

The input schema provides 100% coverage for all 5 parameters, each with at least an example or allowed values (e.g., 'Default or Media' for searchType, 'Relevance or Recency or Likes' for rankingMode). The description adds no extra semantic meaning beyond naming communityId, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Get') and resource ('Community Tweets') and identifies the key input ('by Community ID'), so it clearly states what the tool does. However, it does not distinguish itself from the similar sibling tool 'get_community_timeline', so it falls short of a perfect 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus the many community-related siblings, nor any exclusions or alternatives. It simply repeats the operation without contextualizing its appropriate use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server