Twitter241 MCP Server

search_community

Search Twitter communities by keyword to discover relevant groups. Specify query and result count to retrieve community listings.

Instructions

Search 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": {
      "query": "<query>",
      "count": "<count>"
    },
    "name": "search_community"
  }
}

Input Schema

Name	Required	Description
`count`	Yes	Example value: 20
`query`	Yes	Example value: football
`cursor`	No	Example value:

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

D1.9/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It discloses nothing beyond the tool name—no mention of pagination via cursor, required count, result format, rate limits, or auth requirements.

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 short but not effectively concise—it is under-specified. It consists of only the string 'Search community', which restates the tool name and provides no informative content, so the single sentence fails to earn its place.

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?

For a tool with three parameters, no output schema, and no annotations, the description should explain what searching a community means, how the query and count are used, and how cursor pagination works. The current description is completely inadequate for an agent to use this tool correctly.

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 schema has 100% description coverage for all three parameters, so the baseline is 3. Although the parameter descriptions are only example values and add little semantic meaning, the schema at least documents the parameter names and required status, and the description adds no additional value.

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 'Search community' is a near-verbatim restatement of the tool name and provides no additional specificity about what is being searched, what kinds of communities are included, or what the result represents. It does not distinguish the tool from sibling tools like search_twitter, search_lists, or search_jobs.

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 gives no indication of when to use this tool versus the many sibling search-related tools. There is no mention of intended use cases, limitations, or alternatives, leaving the agent with no guidance for selection.

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

Deploy Server