SocialDataX 百度贴吧 MCP

baidu_tieba_search_users

Read-only

按关键词查找百度贴吧用户，返回精确匹配和相关用户的单页结果，不支持分页。

结果中的 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": {
      "keyword": "<keyword>"
    },
    "name": "baidu_tieba_search_users"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	用户名称关键词，例如美食、旅行；不要传用户主页链接、数字用户 ID 或分页令牌。

Output Schema

Name	Required	Description
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`exact_matches`	Yes	精确匹配用户列表；没有精确匹配时为空数组。
`related_users`	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
```
Changed17 schema fields changedNov 3, 2026
- addedOutput schema / properties / exact_matches / items / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / exact_matches / items / properties / bio / title
```
Added value: +"Bio"
```
- addedOutput schema / properties / exact_matches / items / properties / follower_count / title
```
Added value: +"Follower Count"
```
- addedOutput schema / properties / exact_matches / items / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / exact_matches / items / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / exact_matches / items / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / exact_matches / items / title
```
Added value: +"TiebaUserSearchItem"
```
- addedOutput schema / properties / exact_matches / title
```
Added value: +"Exact Matches"
```
- addedOutput schema / properties / related_users / items / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / related_users / items / properties / bio / title
```
Added value: +"Bio"
```
- addedOutput schema / properties / related_users / items / properties / follower_count / title
```
Added value: +"Follower Count"
```
- addedOutput schema / properties / related_users / items / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / related_users / items / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / related_users / items / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / related_users / items / title
```
Added value: +"TiebaUserSearchItem"
```
- addedOutput schema / properties / related_users / title
```
Added value: +"Related Users"
```
- addedOutput schema / title
```
Added value: +"TiebaUserSearchResult"
```
First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description still adds real behavioral context by disclosing single-page results with no pagination, which prevents an agent from attempting page-token loops. It stops short of describing match ordering or approximate result volume.

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?

Two sentences, zero filler: capability and scope first, then the routing hint and the profile_url follow-up. The no-pagination constraint is stated up front rather than buried.

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 fields including profile_url need no explanation, and the description correctly explains what to do with profile_url next. The only minor gap is that it does not say whether results are capped or how exact versus related matches are ordered.

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 schema already warns against passing profile links, numeric user IDs, or pagination tokens, so the description's "按关键词" adds little beyond confirming the input is a free-text keyword. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ("按关键词查找百度贴吧用户") and scopes the output ("返回精确匹配和相关用户的单页结果"), which separates it cleanly from the post-, forum-, and general-search siblings that share the same search namespace.

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 alternative path: when a user homepage link already exists, call the user-profile or user-posts tools directly instead of searching. That is exactly the when-not guidance an agent needs, and it maps onto the *_by_profile_url 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?