AIsa X / Twitter

Get Community Tweets

get_twitter_community_tweets_all

Read-onlyIdempotent

Search posts across all X Communities by keyword, sorted by Latest (default) or Top, cursor-paginated. Use this to find topic-specific discussion happening inside communities rather than on the public timeline — signal density is usually higher and noise lower. Returns full tweet objects. Once you identify a community worth following, use get_twitter_community_tweets to read it directly, or get_twitter_community_info for its metadata. For public-timeline search use get_twitter_tweet_advanced_search.

Usage-based billing; Default request estimate: $0.003 USD (not a fixed price). Account-specific pricing and final settlement may differ.

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

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query (e.g., keyword)
`cursor`	No	Cursor for pagination
`queryType`	Yes	Query type (Latest or Top)	Latest

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world behavior, so the bar is lower. The description adds useful context—cursor pagination, sort options, and that full tweet objects are returned—though it omits billing implications beyond the appended pricing note and rate-limit behavior.

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

Conciseness4/5

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

Front-loaded with the core action and scope, followed by a compact usage rationale and sibling routing. The appended pricing block adds tokens but is operational metadata rather than the description's own prose.

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

Completeness4/5

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

Complete enough for a 3-param search tool with full schema coverage, annotations, and an output schema. It covers scope, sorting, pagination, and siblings; only deeper behavioral details like error modes or limits are absent.

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%, so the schema documents query, cursor, and queryType. The description mentions sorting by Latest/Top and cursor-paginated results but adds no syntax, format, or filter semantics beyond what the schema already provides, so baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb (Search), resource (posts across all X Communities), and scope (by keyword, sorted, paginated). It explicitly distinguishes itself from the public-timeline sibling and names the narrower community tool.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rationale (topic-specific community discussion, higher signal density) and routes to siblings: get_twitter_community_tweets for a single community, get_twitter_community_info for metadata, and get_twitter_tweet_advanced_search for public timeline.

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

All AIsa X / Twitter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?