AIsa X / Twitter

Get User Info

get_twitter_user_info

Read-onlyIdempotent

Look up one X (Twitter) user's public profile by @handle (screen name). Use this when you need to know who an account is — identity, reach, or credibility — before deciding whether to trust or analyze their content. Returns display name, bio, follower/following counts, verification status, account creation date, location, and profile images. If you only have a numeric user ID, use get_twitter_user_batch_info_by_ids instead. If you need extended profile metadata such as country or username-change history, use get_twitter_user_about. If you want their posts rather than their profile, use get_twitter_user_tweet_timeline.

Published reference price: $0.00018 USD per successful request. 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_info"
  }
}

Input Schema

Name	Required	Description	Default
`userName`	Yes	The screen name of the user

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"
+]
```
Changed1 schema field changedOct 19, 2026
- addedInput schema / properties / userName / description
```
Added value: +"The screen name of the user"
```
Changed2 schema fields changedOct 15, 2026
- removedInput schema / properties / userName / description
```
Removed value: -"The screen name of the user"
```
- 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 establish readOnly, idempotent, non-destructive, open-world, so the bar is lower. The description adds useful behavioral context: the single-user scope, the returned field set, and a published per-request price note. It does not cover error behavior for suspended/private accounts, but that is a minor gap given the annotation coverage.

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 the core verb and resource, then alternatives, then return values — a sensible order. The only slack is the injected pricing boilerplate, which is not part of the tool's semantics but is short.

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?

An output schema exists, so return values need not be explained, yet the description still summarizes them. For a one-parameter read-only lookup with full annotation coverage, an agent has everything needed to select and invoke 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?

With 100% schema coverage the baseline is 3, but the description adds meaning the schema does not: the parameter is specifically an @handle/screen name, and numeric IDs must go to the batch tool. That disambiguates the input format concretely.

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?

Specific verb and resource: 'Look up one X (Twitter) user's public profile by @handle (screen name)'. It also enumerates what the profile contains, making it easy to distinguish from timeline, about, and batch-lookup siblings.

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?

Explicit when-to-use ('when you need to know who an account is — identity, reach, or credibility') plus three named alternatives with the exact condition that selects each: numeric ID → batch_info_by_ids, extended metadata → user_about, posts → tweet_timeline.

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?