Skip to main content
Glama
Sign In
x-mcp-server

x-mcp-server

by lluisfont
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

x_get_user_posts

Read-only

Fetch recent posts from a specific X user ID. Use to access a user's latest posts for tracking or research.

Instructions

Get recent posts authored by an X user ID.

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": {
      "userId": "<userId>"
    },
    "name": "x_get_user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes
maxResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one useful behavioral trait, that only 'recent' posts are returned (not full history), but it never defines that window or says anything about pagination or ordering.

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?

A single front-loaded sentence with no wasted words. It is efficient, though arguably under-specified rather than optimally concise.

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

Completeness2/5

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

For a low-complexity two-parameter tool with no output schema, an agent still lacks what 'recent' means, how many posts come back, whether the list is paginated, and what fields are returned. The definition is too thin to call correctly with confidence.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, yet it only restates that userId is an X user ID. maxResults is entirely unaddressed in the description; the schema supplies default/min/max but no meaning for the value or how results are paged.

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

Purpose4/5

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

Names a specific verb and resource ('Get recent posts authored by an X user ID'), so the agent knows exactly what is retrieved. It does not distinguish itself from siblings like x_search_posts or x_get_post, but the by-user scoping is still clear.

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 when-to-use guidance, no mention of alternatives (e.g. x_search_posts for query-based retrieval, x_get_post for a single post), and no prerequisites such as requiring a user ID from x_get_user or x_get_me.

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

Deploy Server

Other Tools