SocialDataX 百度贴吧 MCP

baidu_tieba_search_general

Read-only

按关键词获取百度贴吧综合搜索中的帖子，保留帖子顺序，支持分页。

不返回吧、用户、话题或搜索建议。需要最新、最早、相关排序时使用帖子搜索；指定帖子链接或 ID 使用详情工具。当前页没有帖子时，仍以 next_page_token 判断能否续页。图片、视频仅来自搜索结果，可能不完整，无法据此判断媒体总数。

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_general"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	搜索词或关键词短语，例如摄影、旅行攻略；不要传帖子链接或分页令牌。
`page_token`	No	分页令牌；首次留空，续页原样传回综合搜索返回的 next_page_token，并保持 keyword 不变；即使 items 为空，只要令牌非空仍可继续翻页。不要使用帖子搜索或评论的分页令牌。

Output Schema

Name	Required	Description
`items`	Yes	当前页帖子列表。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`next_page_token`	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
```
Changed32 schema fields changedNov 3, 2026
- addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / items / items / properties / author / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / items / items / properties / author / title
```
Added value: +"TiebaSearchAuthor"
```
- addedOutput schema / properties / items / items / properties / forum_id / title
```
Added value: +"Forum Id"
```
- addedOutput schema / properties / items / items / properties / forum_name / title
```
Added value: +"Forum Name"
```
- addedOutput schema / properties / items / items / properties / images / items / properties / height / title
```
Added value: +"Height"
```
- addedOutput schema / properties / items / items / properties / images / items / properties / url / title
```
Added value: +"Url"
```
- addedOutput schema / properties / items / items / properties / images / items / properties / width / title
```
Added value: +"Width"
```
- addedOutput schema / properties / items / items / properties / images / items / title
```
Added value: +"TiebaSearchImage"
```
- addedOutput schema / properties / items / items / properties / images / title
```
Added value: +"Images"
```
- addedOutput schema / properties / items / items / properties / like_count / title
```
Added value: +"Like Count"
```
- addedOutput schema / properties / items / items / properties / post_url / title
```
Added value: +"Post Url"
```
- addedOutput schema / properties / items / items / properties / publish_time / title
```
Added value: +"Publish Time"
```
- addedOutput schema / properties / items / items / properties / share_count / title
```
Added value: +"Share Count"
```
- addedOutput schema / properties / items / items / properties / summary / title
```
Added value: +"Summary"
```
- addedOutput schema / properties / items / items / properties / thread_id / title
```
Added value: +"Thread Id"
```
- addedOutput schema / properties / items / items / properties / title / title
```
Added value: +"Title"
```
- addedOutput schema / properties / items / items / properties / update_time / title
```
Added value: +"Update Time"
```
- addedOutput schema / properties / items / items / properties / videos / items / properties / cover_image_url / title
```
Added value: +"Cover Image Url"
```
- addedOutput schema / properties / items / items / properties / videos / items / properties / duration_ms / title
```
Added value: +"Duration Ms"
```
- addedOutput schema / properties / items / items / properties / videos / items / properties / height / title
```
Added value: +"Height"
```
- addedOutput schema / properties / items / items / properties / videos / items / properties / play_count / title
```
Added value: +"Play Count"
```
- addedOutput schema / properties / items / items / properties / videos / items / properties / video_url / title
```
Added value: +"Video Url"
```
- addedOutput schema / properties / items / items / properties / videos / items / properties / width / title
```
Added value: +"Width"
```
- addedOutput schema / properties / items / items / properties / videos / items / title
```
Added value: +"TiebaSearchVideo"
```
- addedOutput schema / properties / items / items / properties / videos / title
```
Added value: +"Videos"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"TiebaPostSearchItem"
```
- addedOutput schema / properties / items / title
```
Added value: +"Items"
```
- addedOutput schema / properties / next_page_token / title
```
Added value: +"Next Page Token"
```
- addedOutput schema / title
```
Added value: +"TiebaPostSearchResult"
```
Changed3 schema fields changedOct 29, 2026
- addedOutput schema / properties / items / items / properties / update_time / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedOutput schema / properties / items / items / properties / update_time / description
```
Previous value: -"更新时间，秒级 Unix 时间戳。"New value: +"更新时间，秒级 Unix 时间戳；未提供时为 null。"
```
- removedOutput schema / properties / items / items / properties / update_time / type
```
Removed value: -"integer"
```
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, but the description adds non-obvious behavior: result order is preserved, pagination continues via next_page_token even when items is empty, and media fields are only as complete as the search result. Those are genuine operational caveats not present in annotations. It stops short of describing anything about auth or rate limits.

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?

Purpose is front-loaded in sentence one, followed by exclusions, alternatives, and pagination edge cases in order of declining importance. Dense but every sentence carries distinct information; 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 two-parameter, read-only search tool with an output schema, the description covers the gaps that matter: ordering, what is excluded, which sibling to use instead, and the empty-page pagination edge case. Nothing an agent needs in order to call it correctly is missing.

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 both parameters are already documented in-schema, including the next_page_token round-trip rule. The description adds nothing parameter-specific beyond what the schema states, so the baseline 3 applies.

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?

It states a specific verb and resource (按关键词获取百度贴吧综合搜索中的帖子) and immediately narrows scope by listing what is not returned (吧、用户、话题、搜索建议). An agent can distinguish this generic post search from baidu_tieba_search_users, baidu_tieba_search_suggestions, and the detail tools without opening any 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?

It routes the agent explicitly: use 帖子搜索 for latest/earliest/relevance sorting, and detail tools when a post link or ID is known. That is a clear when-to-use-elsewhere statement naming the alternative tool families, not just implied context.

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?