SocialDataX 百度贴吧 MCP

baidu_tieba_search_posts_in_forum

Read-only

按准确贴吧名称和关键词搜索该吧主题帖，支持最新或相关排序及分页，不搜索评论。

不限定贴吧时使用全站帖子搜索；返回摘要及可能不完整的图片和视频。

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": {
      "forum_name": "<forum_name>",
      "keyword": "<keyword>"
    },
    "name": "baidu_tieba_search_posts_in_forum"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	在指定贴吧中搜索的关键词或短语；不要传帖子链接或分页令牌。
`sort_type`	No	排序方式：newest 为最新（默认），relevance 为相关；relevant 仅兼容旧调用，新调用请使用 relevance。结果顺序以贴吧返回为准。	newest
`forum_name`	Yes	准确贴吧名称，例如方便面；直接使用结果中的 forum_name，不要自行追加“吧”字；不要传 URL 或数字 ID，无需 URL 编码。
`page_token`	No	分页令牌；首次留空，续页原样传入本接口返回的 next_page_token，保持 forum_name、keyword、sort_type 不变；不要使用其他搜索接口的令牌。

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

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context on scope (threads only, not comments) and on return quality (summaries plus possibly incomplete images/videos). That warns the agent about partial media before it commits to a reliance story. No auth, rate-limit, or pagination-depth details beyond the passing mention of 分页.

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 compact sentences: the first front-loads what the tool does and its scope limits, the second handles the alternative-route rule and the return caveat. Nothing is redundant with the schema or annotations, and every clause carries decision-relevant information.

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?

Four parameters with full schema coverage, an output schema for return shape, and readOnly/openWorld annotations covering the safety profile. The description fills the remaining gaps an agent needs: scope (threads not comments), sorting and pagination support, the site-wide alternative, and the media-completeness caveat.

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%, so the schema already carries sort_type enum semantics, the exact forum_name format, and page_token continuation rules. The description only restates that exact forum name and keyword drive the search, adding no syntax or edge-case meaning beyond the schema. 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?

States a specific verb and resource (搜索该吧主题帖) plus the exact scope constraints (按准确贴吧名称和关键词, 不搜索评论). It also delineates itself from the site-wide post search, so an agent can distinguish it from baidu_tieba_search_posts and baidu_tieba_search_general without opening a schema.

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

Usage Guidelines4/5

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

The description gives an explicit routing rule: when the forum is not fixed, use the site-wide post search instead. It also excludes comments as a target, which prevents misuse against the comment siblings. It falls short of 5 because it never names the alternative sibling tools directly, leaving the agent to map the phrase to a specific name.

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?