Skip to main content
Glama

twitr.sh

by sh.twitr

x_community

Manage X/Twitter Communities as a connected account: create a new community, join or leave an existing one, or delete a community you own.

Guidance: PREREQUISITE: connect an X account. Acts as a handle THIS wallet owns. action=create (name, optional description) | join|leave (community_id) | delete (community_id + community_name confirmation). account required. Payment settles before the action; Idempotency-Key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNocreate: the community name.
actionYesWhich community action.
accountYesA connected X handle owned by this wallet (no @).
descriptionNocreate: optional community description.
community_idNojoin|leave|delete: the community ID.
community_nameNodelete: the community name, as confirmation.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Discloses payment settlement and idempotency-key requirement, and that the tool acts on a connected handle. However, no safety warnings about deletion irreversibility or error behaviors, and no discussion of rate limits or authorization beyond account requirement. With no annotations, more behavioral context would be beneficial.

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?

Two paragraphs: purpose statement then guidance. Front-loaded with main functionality. Efficient but could be slightly more structured (e.g., bullet points). No wasted words.

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

Completeness3/5

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

Covers action mapping, prerequisites, and key constraints (payment, idempotency). Missing details on how to obtain community IDs, error handling, or post-action outcomes. Adequate but not fully complete given the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds value by mapping actions to parameters (e.g., create requires name, delete requires community_id and community_name) and noting optional fields. This explains conditional usage beyond schema.

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?

Clearly states it manages X/Twitter communities with four specific actions (create, join, leave, delete). Distinguishes from sibling tools like x_communities (likely for listing) and other X tools.

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

Usage Guidelines4/5

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

Provides explicit prerequisite (connected X account), action-to-parameter mapping, and required fields. Lacks explicit when-not-to-use or alternatives, but the action-specific guidance is clear.

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

All twitr.sh toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (write, read, search, monitor, compose, etc.), but some overlaps exist: x_read includes trending topics while x_radar is dedicated to trends, and x_timeline provides engagement lists that overlap with x_extract's extractors. Descriptions help differentiate them, but an agent might initially confuse the boundary between x_read, x_search, and x_timeline for tweet retrieval.

Naming Consistency4/5

All tool names share the x_ prefix and are single words, but mix verb forms (read, search, write, compose, extract, monitor) with noun forms (draws, radar, inbox, lists, profile, timeline). The convention is predictable and uniformly lowercase, but a fully consistent verb_noun or noun-only pattern would be clearer. Minor deviation: x_communities vs x_community are nearly identical and refer to reading vs managing.

Tool Count5/5

14 tools is well within the ideal 3-15 range and each tool covers a distinct functional area of X/Twitter: reading, writing, searching, monitoring, extracting, composing, community management, etc. The count feels appropriate for the broad scope of the server, neither bloated nor thin.

Completeness5/5

The tool surface covers the major X/Twitter interactions comprehensively: fully capable read (x_read, x_search, x_timeline), write (x_write, x_profile), community and list operations, real-time monitoring, bulk extraction, direct messaging, media, trends, and even AI-assisted composition and giveaways. Obvious gaps are minimal, such as no list creation/management commands, but the core lifecycle of tweets, users, communities, and accounts is well covered.

Resources