Skip to main content
Glama

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

x_user_mentions

Get user mentions. Tweets that mention a user. 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_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor. Leave empty for the first page, then pass `next_cursor` from the previous response.
userNameYesScreen name without the @, e.g. `NASA`.
sinceTimeNoOnly items created at or after this Unix timestamp (seconds).
untilTimeNoOnly items created before this Unix timestamp (seconds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose one genuine behavioral trait – that results are paginated via cursor/next_cursor. It says nothing about ordering, result caps, rate limits, or permission requirements, which are the remaining unknowns for a read endpoint with no safety annotations.

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 with the core purpose front-loaded and no filler. The trailing pagination sentence partly duplicates the cursor parameter's own schema text, but it is brief enough not to be waste.

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?

For a 4-parameter read tool with no annotations and no output schema, the description covers purpose and pagination but leaves the return shape, ordering, and result limits unstated. It is adequate to make the call correctly but thin on what to expect back.

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 all four parameters (including the userName-without-@ format and the sinceTime/untilTime Unix seconds semantics) are already fully documented in the schema. The description only restates the cursor mechanism, adding no meaning beyond structured data – baseline 3.

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 verb+resource ("Get user mentions") is immediately disambiguated by the follow-up "Tweets that mention a user," which removes the ambiguity about whether the result is users or tweets. It does not differentiate itself from near-neighbors such as x_user_tweet_timeline or x_user_search, so an agent must still infer which endpoint yields mentions.

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 by the phrase "Get user mentions" – an agent can infer it is the right call when looking for tweets referencing a screen name. There is no explicit when-to-use or when-not-to-use guidance and no pointer to a sibling for the adjacent cases (search, timeline, replies).

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