Skip to main content
Glama

twitr.sh

by sh.twitr

x_lists

Read an X/Twitter List: its combined tweet timeline, its member roster, or its followers. Billed per item returned. Useful for following a curated set of accounts as one feed.

Guidance: kind=tweets|members|followers; id = list ID. resultsLimit is MANDATORY — billed per item returned. tweets supports sinceTime/untilTime and includeReplies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesList ID.
kindYesWhat to read from the list.
sinceTimeNo
untilTimeNo
resultsLimitYesMANDATORY: max items returned, billed per item.
includeRepliesNo

Schema Changelog

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

  1. First observed

TDQS

A4.2/5.0
Behavior3/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. It clearly states the tool is for reading, but does not disclose any rate limits, authentication requirements, error behavior, or pagination details. The billing mention adds some transparency, but more behavioral context would be helpful.

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 concise and well-structured, with two clear paragraphs: the first states the tool's purpose, the second provides usage guidance. Every sentence adds value without unnecessary words.

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?

Given the tool has 6 parameters (3 required), no output schema, and moderate complexity, the description covers the essential aspects: what it reads, how to specify kind and ID, mandatory resultsLimit, and optional time filters for tweets. It does not explain return format or error conditions, but for a read tool with no output schema, it is fairly complete.

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?

The description adds significant meaning beyond the input schema. It explains the possible values for 'kind' (tweets, members, followers), clarifies that 'id' is a list ID, emphasizes that 'resultsLimit' is mandatory and billed per item, and notes that 'sinceTime', 'untilTime', and 'includeReplies' are supported only when kind=tweets. Schema coverage is 50%, and the description compensates well.

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?

The description clearly states the verb 'Read' and specifies the resource (an X/Twitter List) along with the three things that can be read: combined tweet timeline, member roster, or followers. This specificity differentiates it from sibling tools like x_timeline or x_search.

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?

The description provides explicit guidance on how to use the tool: it explains the 'kind', 'id', and mandatory 'resultsLimit' parameters, and notes that for 'tweets', optional 'sinceTime', 'untilTime', and 'includeReplies' are available. It also mentions billing per item. However, it does not explicitly state when not to use this tool or suggest alternative tools.

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