Skip to main content
Glama

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

x_article

Get article. An article (long-form post) by its tweet 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": {
      "tweet_id": "<tweet_id>"
    },
    "name": "x_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
tweet_idYesNumeric tweet ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about access requirements, behavior for deleted/protected/non-article tweets, or rate limits. 'Get' weakly implies a read, but with zero annotation coverage the description should be explicit about safety and failure modes and is not.

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 short sentences with the resource stated first and the key needed to call it second - nothing wasted, nothing buried. The second sentence is slightly redundant with the name but earns its place by defining 'article'.

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?

This is a simple one-parameter read, and the description covers what it fetches and by what key. However, with no output schema, the description never indicates what an article response contains (full text, title, author, media), leaving a meaningful gap for a content-retrieval tool.

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 coverage is 100% and the single parameter tweet_id is already documented as a 'Numeric tweet ID' in the schema. The description's phrase 'by its tweet ID' adds only marginal meaning - it implies the ID identifies the tweet that hosts the article - so the schema does the heavy lifting.

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?

The description names a specific verb ('Get') and resource ('article'), and the parenthetical '(long-form post)' disambiguates what an article is, which is genuinely useful. It stops short of differentiating itself from plausible siblings such as x_tweets or x_user_articles, so an agent must still infer the boundary.

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?

The phrase 'by its tweet ID' hints at the required retrieval key but gives no when-to-use guidance, no prerequisites, and no named alternative for fetching articles by user (x_user_articles) versus a single article. The agent is left to infer selection logic entirely from the tool name.

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