Vee3

x-twitter.user_info

Fetch public profile metadata for an X (Twitter) user.

Provide user_name (handle without @) or rest_id (numeric user id). At least one is required. When rest_id is set, it takes precedence over user_name. Returns display name, bio, follower counts, verification flags, avatar URLs, and related profile fields.

Cost = 2 tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`rest_id`	No	Numeric X user id (rest_id). When provided, user_name is ignored.
`user_name`	No	X handle without the leading @ (for example elonmusk). Required when rest_id is omitted.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Numeric X user id (may duplicate rest_id).
`desc`	No	Profile bio / description.
`name`	No	Display name shown on the profile.
`avatar`	No	Profile avatar image URL.
`status`	No	Profile lookup status from the upstream provider.
`friends`	No	Number of accounts the user follows.
`profile`	No	X screen name (handle).
`rest_id`	No	Numeric X user id.
`location`	No	Profile location string.
`protected`	No	Whether the account is protected (private).
`sub_count`	No	Follower count.
`affiliates`	No	Affiliate account metadata when present (object or empty array from the provider). Additional provider-specific fields may appear.
`created_at`	No	Account creation timestamp from X.
`media_count`	No	Total media item count.
`header_image`	No	Profile banner image URL.
`blue_verified`	No	Whether the account has X blue verification.
`statuses_count`	No	Total post count.
`business_account`	No	Business account metadata when present (object with counts or empty array from the provider when not applicable).
`verification_type`	No	Verification type label from X when present.
`pinned_tweet_ids_str`	No	Pinned tweet ids for the profile when present.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedJun 21, 2026

changedInput schema / properties / rest_id / description

Previous value: -"Numeric X user id (rest_id). When provided, screenname is ignored."New value: +"Numeric X user id (rest_id). When provided, user_name is ignored."

removedInput schema / properties / screenname

Removed value: -{
-  "anyOf": [
-    {
-      "maxLength": 50,
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "X handle without the leading @ (for example elonmusk). Required when rest_id is omitted.",
-  "title": "Screenname"
-}

addedInput schema / properties / user_name

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 50,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "X handle without the leading @ (for example elonmusk). Required when rest_id is omitted.",
+  "title": "User Name"
+}

Changed9 schema fields changedJun 18, 2026

addedOutput schema / $defs / GetXUserInfoResponseBusinessAccount

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "affiliates_count": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Number of affiliate accounts when provided.",
+      "title": "Affiliates Count"
+    },
+    "category": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/GetXUserInfoResponseBusinessAccountCategory"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Business category metadata when provided."
+    }
+  },
+  "title": "GetXUserInfoResponseBusinessAccount",
+  "type": "object"
+}

addedOutput schema / $defs / GetXUserInfoResponseBusinessAccountCategory

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Business category id.",
+      "title": "Id"
+    },
+    "name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Business category name.",
+      "title": "Name"
+    }
+  },
+  "title": "GetXUserInfoResponseBusinessAccountCategory",
+  "type": "object"
+}

removedOutput schema / $defs / GetXUserInfoResponseBusinessAccountItem

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "category": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/GetXUserInfoResponseBusinessAccountItemCategory"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Business category metadata when provided."
-    }
-  },
-  "title": "GetXUserInfoResponseBusinessAccountItem",
-  "type": "object"
-}

removedOutput schema / $defs / GetXUserInfoResponseBusinessAccountItemCategory

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "id": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Business category id.",
-      "title": "Id"
-    },
-    "name": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Business category name.",
-      "title": "Name"
-    }
-  },
-  "title": "GetXUserInfoResponseBusinessAccountItemCategory",
-  "type": "object"
-}

removedOutput schema / $defs / GetXUserInfoResponsePinnedTweetIdsStrItem

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "tweet_id": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Numeric tweet id.",
-      "title": "Tweet Id"
-    }
-  },
-  "title": "GetXUserInfoResponsePinnedTweetIdsStrItem",
-  "type": "object"
-}

changedOutput schema / properties / business_account / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/GetXUserInfoResponseBusinessAccountItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/GetXUserInfoResponseBusinessAccount"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / business_account / description

Previous value: -"Business account metadata when present (object with counts or array entries depending on the provider response)."New value: +"Business account metadata when present (object with counts or empty array from the provider when not applicable)."

removedOutput schema / properties / business_account / title
```
Removed value: -"Business Account"
```

changedOutput schema / properties / pinned_tweet_ids_str / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/GetXUserInfoResponsePinnedTweetIdsStrItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

First observedJun 18, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It clearly indicates a read operation via 'Fetch' and notes that it returns public data, plus the cost in tokens. It does not explicitly state 'read-only' or mention rate limits/errors, but for a simple fetch tool the behavior is reasonably transparent.

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?

The description is three sentences, front-loaded with the purpose, then parameter usage, then return fields and cost. Every sentence is informative with no fluff.

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

Completeness4/5

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

The tool is simple (2 parameters) and has an output schema that covers return structure. The description lists key fields and any constraints, making it sufficiently complete. It omits error cases or rate limits, but these are not critical for this straightforward fetch tool.

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 description coverage is 100%, so baseline is 3. The description adds value by clarifying that at least one parameter is required and that rest_id takes precedence over user_name when both are provided, which goes beyond the schema descriptions.

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 description uses a specific verb ('Fetch') and resource ('public profile metadata for an X (Twitter) user'), making the tool's purpose clear. However, it does not explicitly differentiate from sibling tools like user_timeline or tweet_info, so it stays at a 4 rather than a 5.

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?

The description implies usage by listing what it returns (display name, bio, follower counts, etc.), which tells the agent what this tool is for. It does not mention alternatives or exclusions (e.g., when to use user_timeline instead), so only implied usage context is provided.

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

All Vee3 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

x-twitter.user_info

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources