TwitterAPI.io MCP Server

Get Mentions of a User

get_user_mentions

Read-only

Fetch tweets that mention a specific Twitter/X user (i.e. tweets containing @userName). Useful for brand monitoring, sentiment tracking on a public figure, or finding conversations involving an account. Supports time-bound queries via sinceTime/untilTime (Unix seconds). Paginates via 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": "get_user_mentions"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Pagination cursor; omit for first page (~20 per page).
`userName`	Yes	Twitter/X screen name without @ — fetches tweets that mention this user (@userName).
`sinceTime`	No	Unix timestamp (seconds) lower bound — only mentions after this time. Omit for no lower bound.
`untilTime`	No	Unix timestamp (seconds) upper bound. Omit for no upper bound.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavioral details beyond this: time-bound queries via sinceTime/untilTime and pagination via cursor. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences: the core operation, the use cases, and the key capabilities. The most important information is front-loaded, and every sentence earns its place.

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 simple read-only mention-fetching tool, the description covers the operation, use cases, time filtering, and pagination. All four parameters are documented in the schema, and no output schema exists, so nothing needed for correct invocation is missing.

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 description does not add significant meaning beyond the schema. It mentions sinceTime/untilTime and cursor, but those are already well documented in the input schema.

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?

The description clearly states a specific verb and resource: 'Fetch tweets that mention a specific Twitter/X user' with an exact definition ('tweets containing @userName'). This unambiguously distinguishes it from siblings like get_tweet_replies, get_tweet_quotes, and get_tweet_retweeters.

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

Usage Guidelines4/5

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

It provides clear context for when to use the tool: brand monitoring, sentiment tracking, and finding conversations involving an account. It does not explicitly name alternatives or exclusions, but the use cases give sufficient guidance.

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

All TwitterAPI.io MCP Server 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?