SocialDataX 百度贴吧 MCP

baidu_tieba_get_user_info_by_profile_url

Read-only

通过百度贴吧用户主页链接读取资料、签名、粉丝数、关注数、累计获赞、吧龄和 IP 属地。

已有 profile_url 时优先使用本工具；链接可取搜索、帖子详情或评论作者的同名字段。仅有数字用户 ID 时使用 baidu_tieba_get_user_info_by_user_id；不返回发帖或回复列表。

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": {
      "profile_url": "<profile_url>"
    },
    "name": "baidu_tieba_get_user_info_by_profile_url"
  }
}

Input Schema

Name	Required	Description	Default
`profile_url`	Yes	百度贴吧用户主页完整链接，形如 https://tieba.baidu.com/home/main?id=…；可取搜索、详情或评论作者的 profile_url，不接受数字用户 ID、昵称或帖子链接。

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.7/5.0

Behavior4/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 real behavioral context beyond that: the exact payload fields, the fact that no post/reply lists are included, and acceptable provenance for the input URL. It stops short of noting rate limits, failure modes for deleted or private profiles, or any pagination behavior, which keeps it below a 5.

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 compact sentences: the first lists the returned fields, the second gives the positive selection rule and input provenance, the third gives the negative rule and the scope limit. The most decision-relevant information is front-loaded and nothing is redundant with the title or schema.

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 single-parameter read tool with an output schema, the description covers everything an agent needs: what is read, how to obtain the required URL, which sibling to use instead, and what is out of scope. Return-value detail is already handled by the output schema, so no gap remains.

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 coverage is 100%, so the schema already carries the format and the negative constraints (no numeric IDs, nicknames, or post links). The description still contributes by telling the agent where a valid profile_url can be obtained, which is meaning the schema does not express. That added provenance is what lifts it above the baseline 3.

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?

States a specific verb and resource (read a Tieba user's profile via profile URL) and enumerates exactly which fields come back: signature, follower count, following count, cumulative likes, account age, and IP location. It also explicitly distinguishes itself from the sibling that takes a numeric ID, so an agent can choose between them 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?

Gives an explicit selection rule: prefer this tool when a profile_url is already in hand, and use baidu_tieba_get_user_info_by_user_id when only a numeric user ID exists. It also names where a valid URL can be sourced from (search results, post detail, comment author) and states the exclusion that no post or reply list is returned, implicitly routing that need to the user-posts siblings.

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?