Skip to main content
Glama

twitr.sh

by sh.twitr

x_inbox

Read a connected X/Twitter account's private surfaces: bookmarks and bookmark folders, notifications, and DM history. Billed per item returned; readable only for handles this wallet connected.

Guidance: PREREQUISITE: connect an X account (see /api/x-accounts/start). Reads act AS that account, so you can only read the inbox of a handle THIS wallet connected. action=bookmarks (optional folderId) | bookmark_folders | notifications (optional type) | dm_history (target_user_id required). bookmarks/notifications/dm_history are billed per item — set resultsLimit (1–10000). account (the connected handle) is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNonotifications: optional filter (e.g. mentions).
maxIdNodm_history: paginate before this message id.
actionYesWhich inbox read to run.
accountYesA connected X handle owned by this wallet (no @).
folderIdNobookmarks: optional folder to read.
resultsLimitNoMax items to return (billed per item); ignored for bookmark_folders.
target_user_idNodm_history: the other party's user id.

Schema Changelog

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

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses critical traits: billing per item returned, the ownership restriction (only for handles this wallet connected), and the 'acts AS that account' behavior. These are non-obvious, significant behaviors that an agent must know before invoking the tool.

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 compact yet comprehensive, front-loading the purpose and organizing guidance into a clear block. Every sentence adds value, with no filler. The slight repetition of 'billed per item' is acceptable given the need to emphasize the cost implication. The structure supports quick scanning by an agent.

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?

The description covers prerequisites, scoping, action selection, billing, and parameter requirements very well. However, it does not describe the return format or pagination behavior beyond the maxId parameter in the schema. Since there is no output schema, a brief note on what each action returns would make it fully complete. Overall, it is highly complete for a complex multi-action tool.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds cross-parameter semantics that the schema lacks. It maps actions to their relevant parameters (e.g., 'action=bookmarks (optional folderId)' and 'dm_history (target_user_id required)') and clarifies the purpose of resultsLimit as a billing control. This enhances understanding beyond the individual parameter descriptions.

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 tool 'Read' a specific resource: 'a connected X/Twitter account's private surfaces' and enumerates the exact surfaces (bookmarks, bookmark folders, notifications, DM history). This specific verb+resource combination distinguishes it from sibling tools like x_timeline or x_profile, which target public or different data.

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?

The description provides explicit prerequisites (connect an X account), explains that reads act as the connected account, and gives conditional parameter guidance (e.g., 'dm_history (target_user_id required)' and 'bookmarks/notifications/dm_history are billed per item — set resultsLimit'). This goes beyond a simple when-to-use by specifying exact usage scenarios and exclusions.

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