Twitter241 MCP Server

get_community_timeline

Get posts from a Twitter community timeline using its topic ID. Use cursor to paginate through results.

Instructions

Explore Community Timeline

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>"
    },
    "name": "get_community_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Example value:
`topicId`	Yes	Example value: 4

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?

With no annotations, the description carries full responsibility for behavioral disclosure. It says 'Explore' but does not state whether this is a read operation, whether it returns a paginated list, or any side effects. The tool's behavior is completely unspecified.

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?

'Explore Community Timeline' is extremely short but under-specified. It is not concise in a useful way; it omits essential information that should be front-loaded. The description would be acceptable only if it were a title, but it fails as a functional description.

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?

This tool has two parameters, no output schema, no annotations, and many sibling tools. The description provides virtually no context about return values, pagination behavior, or relationship to other community endpoints. It is far too incomplete for an agent to invoke it 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?

Schema coverage is 100% (both parameters have description fields), so the baseline is 3. However, the descriptions are only example values ('4', empty) and the tool description adds no meaning beyond the parameter names cursor and topicId. While the description doesn't help, the schema technically covers the fields.

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 'Explore Community Timeline' merely restates the tool's name in a different form, acting as a tautology. It doesn't specify what the timeline contains (e.g., posts, tweets) or how it differs from siblings like get_community_tweets. This lacks clear verb+resource+scope.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusion criteria. The description gives no situational signals, making it impossible for an agent to choose this over sibling timeline tools.

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

Deploy Server