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.

Input Schema

Name	Required	Description
`cursor`	No	The cursor to paginate through the results. First page is empty.
`userName`	No	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.

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 readOnly/idempotent/non-destructive/open-world, so the burden is lower. The description still adds real behavioral context: page size (20 per page) and the unique time-window capability. The return-format note (has_next_page/next_cursor) is redundant against the output schema, so it isn't a full 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-loads purpose then usage then return shape in a sensible order, with no filler sentences. The trailing auto-injected pricing comment is noise but boilerplate; the return-value sentence is mildly redundant given the output schema.

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?

For a read-only, paginated list endpoint with a full output schema and safety annotations, the description covers purpose, when-to-use, the time-window mechanics, and pagination size. An agent has everything needed to call it correctly.

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% — sinceTime and untilTime have no schema description. The description compensates by telling the agent these are Unix timestamps in seconds and that they bound the range, which is exactly the missing semantic detail. cursor and userName are already schema-documented, so it 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 differentiates itself from the sibling for own-posts content. An agent can tell it apart from get_twitter_user_last_tweets without reading 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 explicit use cases (monitoring, brand mentions, inbound replies, reputation tracking, 'last 24 hours') and names the alternative ('For the account's own posts... use get_twitter_user_tweet_timeline'). It also declares a differentiating constraint — the only user-scoped X endpoint with a time window — which routes the agent decisively.

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?