Twitter241 MCP Server

fetch_popular_community

Fetch popular communities for a specific topic ID, returning a specified count with optional cursor-based pagination.

Instructions

Fetch Popular Community

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": {
      "topicId": "<topicId>",
      "count": "<count>"
    },
    "name": "fetch_popular_community"
  }
}

Input Schema

Name	Required	Description
`count`	Yes	Example value: 20
`cursor`	No	Example value:
`topicId`	Yes	Get this value from GET /community-topics

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

D1.7/5.0

Behavior1/5

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

No annotations exist, and the description discloses nothing about the tool's behavior. It does not mention return format, pagination behavior, required permissions, or any side effects. The agent gains no insight beyond the tool's name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only three words, which is not conciseness but under-specification. It omits essential details and does not earn its place as a meaningful explanation. A concise description can still be informative; this one is not.

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

Completeness1/5

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

With no output schema, no annotations, and only a vague three-word description, the tool is severely under-specified. There is no explanation of what 'popular community' means, how the parameters interact, or what the response looks like. This is inadequate for safe invocation.

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% since every parameter has a description. However, these descriptions are minimal (e.g., 'Example value: 20', 'Get this value from GET /community-topics'). The tool description itself adds nothing beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Fetch Popular Community' essentially restates the tool name without adding specificity. It does not clarify whether it fetches a single popular community, a list of popular communities, or popular content within a community, nor does it distinguish itself from siblings like get_community_details or get_community_timeline.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No context, prerequisites, or exclusions are provided. The agent is left without any decision framework for choosing this tool over the many community-related siblings.

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

Deploy Server