SocialDataX 百度贴吧 MCP

baidu_tieba_get_user_info_by_user_id

Read-only

仅有百度贴吧数字用户 ID 时读取用户资料及主页统计；已有 profile_url 时优先使用 baidu_tieba_get_user_info_by_profile_url。

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": {
      "user_id": "<user_id>"
    },
    "name": "baidu_tieba_get_user_info_by_user_id"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes	百度贴吧数字用户 ID，可取搜索、帖子详情或评论作者的 user_id；不是主页链接中的 portrait 或 tieba_uid。

Output Schema

Name	Required	Description
`bio`	Yes	用户个人签名；未提供时为空字符串。
`name`	Yes	用户显示名称。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`user_id`	Yes	用户 ID，以字符串表示，可用于查询用户资料。
`tieba_age`	Yes	贴吧展示的吧龄，单位年，保留显示精度，例如 9.2；不是注册日期。
`avatar_url`	Yes	用户头像链接。
`ip_location`	Yes	用户资料显示的 IP 属地。
`profile_url`	Yes	用户主页链接，可用于再次查询用户资料。
`follower_count`	Yes	粉丝数。
`following_count`	Yes	关注数。
`received_like_count`	Yes	累计获赞数。

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```
Changed11 schema fields changedNov 3, 2026
- addedOutput schema / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / bio / title
```
Added value: +"Bio"
```
- addedOutput schema / properties / follower_count / title
```
Added value: +"Follower Count"
```
- addedOutput schema / properties / following_count / title
```
Added value: +"Following Count"
```
- addedOutput schema / properties / ip_location / title
```
Added value: +"Ip Location"
```
- addedOutput schema / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / received_like_count / title
```
Added value: +"Received Like Count"
```
- addedOutput schema / properties / tieba_age / title
```
Added value: +"Tieba Age"
```
- addedOutput schema / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / title
```
Added value: +"TiebaUserInfoResult"
```
First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior3/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. The description adds that the payload includes homepage statistics as well as the profile, which is modest extra value, but it says nothing about behavior for nonexistent or deleted IDs, rate limits, or partial results. With annotations carrying the safety burden, a 3 is appropriate.

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?

A single compact sentence pair with the positive condition front-loaded and the sibling fallback second. No redundant restatement of the tool name or the parameter.

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?

An output schema exists, so return values need not be explained, and the single required parameter is fully documented in the schema. What remains unaddressed is failure behavior for invalid or nonexistent IDs, which would be useful for a single-purpose lookup but is not strictly required.

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 coverage is 100% and the user_id schema text is already detailed, noting that it can come from search, thread detail, or comment authors and is not the portrait or tieba_uid from a homepage URL. The description adds no meaning beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource (read user profile and homepage stats) and immediately scopes it to the case where only a numeric Tieba user ID is available. It explicitly distinguishes itself from the sibling baidu_tieba_get_user_info_by_profile_url, so an agent can choose between the two without opening 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?

Both directions are stated: use this tool when you only hold a numeric user ID, and prefer baidu_tieba_get_user_info_by_profile_url when a profile URL exists. The selecting condition and the named alternative are explicit, leaving nothing to inference.

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

All SocialDataX 百度贴吧 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?