Twitter241 MCP Server

get_community_members

Retrieve Twitter community members by providing the community ID. Use the optional cursor for pagination to fetch all members.

Instructions

Get Community Members 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>"
    },
    "name": "get_community_members"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Example value:
`communityId`	Yes	Example value: 1601841656147345410

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. It only states 'Get Community Members' and does not mention pagination (despite the cursor parameter), rate limits, required permissions, return format, or any side effects. The 'get' implies read-only, but this is not explicit.

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, concise sentence that is front-loaded with the core action and target parameter. There is no wasted wording, making it appropriately sized.

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?

The tool has no output schema, no annotations, and a minimal description. It does not explain pagination (cursor), potential return structure, or usage context. For a list-returning tool with a cursor parameter, the description is insufficiently complete.

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% (both parameters have descriptions), so the baseline is 3. The tool description mentions communityId but not cursor, and the schema descriptions are only example values, adding minimal semantic meaning. No additional parameter context is provided in the description.

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 clearly states the tool retrieves community members using a community ID, with a specific verb and resource. However, it does not explicitly distinguish this from sibling tools like get_community_moderators or get_community_timeline, which also retrieve community-related data.

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 alternatives. Given the many community-related sibling tools, an agent would not know if this is the right choice for fetching members vs. moderators or other community data.

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

Deploy Server