Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_user_articles

Get user's articles. Articles (long-form posts) published by a user. The list is inside data.articles. Paginated: use cursor / next_cursor.

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": {
      "username": "<username>"
    },
    "name": "x_user_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor. Leave empty for the first page, then pass `next_cursor` from the previous response.
usernameYesScreen name without the @.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two useful behaviors beyond the schema: where results live (`data.articles`) and that the endpoint is paginated via cursor/next_cursor. It says nothing about auth requirements, ordering, page size, or what an empty/private-account result looks like.

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?

Three short sentences, front-loaded with the action, then the resource clarification, then the response path and pagination. Minor redundancy between "Get user's articles" and "Articles ... published by a user", but nothing is wasted.

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?

For a two-parameter read tool with no output schema, the description covers the essential items an agent needs: what it returns, where the payload sits, and how to paginate. Only secondary details like ordering or page 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 description coverage is 100%, so the schema already documents both `username` (screen name without @) and `cursor` (pass next_cursor from previous response). The description merely restates the cursor/next_cursor pattern, adding no new parameter meaning; baseline 3 applies.

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?

States a specific verb and resource ("Get user's articles") and clarifies that articles are long-form posts published by a user, which separates it from the tweet-timeline siblings. It doesn't explicitly name a sibling to distinguish from (e.g. x_article for a single article), but the resource scope is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical "long-form posts" hints at when to pick this over a tweet timeline, but there is no explicit when-to-use, when-not, or named alternative such as x_article or x_user_tweet_timeline.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources