AIsa X / Twitter

Get User Mentions

get_twitter_user_mentions

Read-onlyIdempotent

Get tweets that mention a given @handle, 20 per page. This is the only user-scoped X endpoint that supports a time window: pass sinceTime and/or untilTime as Unix timestamps in seconds to bound the range. Use this for monitoring — brand mentions, inbound replies, reputation tracking, or 'what happened to this account in the last 24 hours'. Returns tweets with has_next_page and next_cursor. For the account's own posts rather than mentions of it, use get_twitter_user_tweet_timeline.

Usage-based billing; Default request estimate: $0.003 USD (not a fixed price). Account-specific pricing and final settlement may differ.

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": "get_twitter_user_mentions"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	The cursor to paginate through the results. First page is empty.
`userName`	Yes	The user screen name to get mentions for.
`sinceTime`	No
`untilTime`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "userName"
+]
```

Changed4 schema fields changedOct 19, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "The cursor to paginate through the results. First page is empty.",
+  "type": "string"
+}

addedInput schema / properties / sinceTime

Added value: +{
+  "maximum": 9223372036854776000,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / untilTime

Added value: +{
+  "maximum": 9223372036854776000,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / userName / description

Added value: +"The user screen name to get mentions for."

Changed5 schema fields changedOct 15, 2026

removedInput schema / properties / cursor

Removed value: -{
-  "description": "The cursor to paginate through the results. First page is empty.",
-  "type": "string"
-}

removedInput schema / properties / sinceTime

Removed value: -{
-  "description": "On or after a specified unix timestamp in seconds.",
-  "format": "int64",
-  "type": "integer"
-}

removedInput schema / properties / untilTime

Removed value: -{
-  "description": "Before a specified unix timestamp in seconds.",
-  "format": "int64",
-  "type": "integer"
-}

removedInput schema / properties / userName / description

Removed value: -"The user screen name to get mentions for."

changedInput schema / required

Previous value: -[
-  "userName"
-]New value: +[]

First observedSep 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, so the description correctly focuses on behavior: 20 results per page, the returned has_next_page/next_cursor fields, and the notable capability claim that this is the only user-scoped X endpoint supporting a time window. It stops short of rate-limit or auth/permission context, which keeps it at 4 rather than 5.

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?

Front-loaded with purpose and scope, then use cases, then return shape, then the sibling alternative — a sensible order. Slightly long with some redundancy between the use-case list and the 'last 24 hours' example, plus appended pricing boilerplate that isn't the author's prose.

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

Completeness5/5

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

Output schema and annotations exist, so the description needn't explain safety or return structures, and it still adds the non-obvious bits: page size, the time-window exclusivity, and the pagination contract. Nothing an agent needs to invoke this correctly is missing.

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

Parameters4/5

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

Schema coverage is only 50%, and the two undocumented parameters (sinceTime, untilTime) are precisely the ones the description explains — Unix timestamps in seconds, used to bound the range. That compensates well for the schema gap; cursor and userName are already covered in the schema, so the description doesn't need to repeat them.

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?

States a specific verb and resource ('Get tweets that mention a given @handle') and immediately distinguishes itself from the closest sibling by naming get_twitter_user_tweet_timeline for the account's own posts. An agent can pick between the two without opening either schema.

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?

Gives concrete when-to-use scenarios (brand mentions, inbound replies, reputation tracking, 'what happened in the last 24 hours') and an explicit when-not-to-use with the named alternative. Both the positive and negative routing conditions are spelled out.

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

All AIsa X / Twitter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?