SocialDataX 微博 Weibo MCP

weibo_get_user_info_by_user_id

Read-only

根据 user_id 获取微博用户资料。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	Yes	微博用户 user_id；可从作者信息或用户资料结果中的非空 user_id 复用。

Output Schema

TableJSON Schema

Name	Required	Description
`bio`	Yes	用户简介；不可用时为空字符串。
`name`	Yes	用户名称；不可用时为空字符串。
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`user_id`	Yes	微博用户 user_id，可作为用户资料或用户帖子列表工具输入。
`verified`	Yes	是否为认证账号。
`avatar_url`	Yes	用户头像链接；不可用时为 null。
`post_count`	Yes	已发布微博数；不可用时为 null。
`profile_url`	Yes	微博用户主页链接；可用于打开用户主页；不可用时为 null；需要继续查询用户资料或用户帖子列表时优先使用非空 user_id。
`follower_count`	Yes	粉丝数；不可用时为 null。
`following_count`	Yes	关注数；不可用时为 null。
`verification_label`	Yes	认证说明；不可用时为 null。

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 8, 2026

addedOutput schema / properties / verification_label

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "认证说明；不可用时为 null。"
+}

removedOutput schema / properties / verified_reason

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "认证说明；不可用时为 null。"
-}

changedOutput schema / required

Previous value: -[
-  "user_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "bio",
-  "follower_count",
-  "following_count",
-  "post_count",
-  "verified",
-  "verified_reason",
-  "points"
-]New value: +[
+  "user_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "bio",
+  "follower_count",
+  "following_count",
+  "post_count",
+  "verified",
+  "verification_label",
+  "points"
+]

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties / points

Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "user_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "bio",
-  "follower_count",
-  "following_count",
-  "post_count",
-  "verified",
-  "verified_reason"
-]New value: +[
+  "user_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "bio",
+  "follower_count",
+  "following_count",
+  "post_count",
+  "verified",
+  "verified_reason",
+  "points"
+]

First observedJun 22, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered elsewhere. The description adds no behavioral context beyond the annotations—nothing about rate limits, auth, or what an external network lookup implies.

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?

A single front-loaded sentence with zero waste. It is appropriately sized for a one-parameter read tool, though it is so terse that it omits all routing guidance.

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

Completeness3/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 described, and the single param is covered by the schema. However, the description omits any signal distinguishing this from the closely named profile_url sibling, which is the main gap for a lookup tool in this family.

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% and there is only one parameter, so the schema fully documents user_id, including reuse guidance. The description adds no additional meaning beyond the schema, making the baseline 3 correct.

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?

States a specific verb+resource (获取微博用户资料) and the lookup key (user_id), which implicitly distinguishes it from the sibling weibo_get_user_info_by_profile_url. It is clear but does not explicitly name or contrast with that alternative.

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

Usage Guidelines2/5

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

Nothing about when to use this versus the profile_url variant, no prerequisites, no exclusions. The only hint is the tool name itself, which the description merely restates.

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

All SocialDataX 微博 Weibo MCP 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?