Twitter241 MCP Server

get_community_details

Get detailed information about a Twitter community by supplying its community ID. Access community metadata and attributes for your analysis.

Instructions

Get Community Details 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_details"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

C2.3/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it retrieves community details, without specifying what data is returned, any authentication requirements, rate limits, or potential side effects. The description adds no behavioral context 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.

Conciseness5/5

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

The description is a single, front-loaded sentence with zero wasted words. It is efficiently structured, though this brevity comes at the cost of substantive content, which is more appropriately penalized under other dimensions.

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 tool's simplicity (one param, no output schema), the description still falls short. It does not explain what 'details' means or what the response contains, and it doesn't help differentiate from the many similar get_community_* tools. The description is too minimal to provide adequate contextual completeness.

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 fully describes the single parameter `communityId` with an example value, achieving 100% schema description coverage. The description adds no new semantic information about the parameter beyond what is already present in the schema, so the baseline of 3 is appropriate.

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 'Get Community Details by Community ID' is essentially a restatement of the tool name, with no additional specification of what 'details' entails. It fails to distinguish from sibling tools like get_community_about or get_community_timeline, making the purpose vague beyond the literal action.

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?

There is no guidance on when to use this tool versus the many other community-related tools. The description provides no context about what makes this the right choice, nor does it mention any exclusions or alternatives.

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

Deploy Server