SocialDataX 百度贴吧 MCP

baidu_tieba_get_post_detail_by_thread_id

Read-only

按主题帖数字 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": {
      "thread_id": "<thread_id>"
    },
    "name": "baidu_tieba_get_post_detail_by_thread_id"
  }
}

Input Schema

Name	Required	Description	Default
`thread_id`	Yes	主题帖数字 ID，可取贴吧搜索结果的 thread_id；不要传帖子链接。

Output Schema

Name	Required	Description
`title`	Yes	帖子标题。
`author`	Yes	帖子作者。
`images`	Yes	首楼图片列表。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`videos`	Yes	首楼视频列表。
`content`	Yes	首楼正文纯文本；表情以“[表情]”表示；无可见正文时为空字符串。
`forum_id`	Yes	所属贴吧 ID，以字符串表示。
`post_url`	Yes	帖子页面链接。
`thread_id`	Yes	主题帖 ID，以字符串表示。
`forum_name`	Yes	帖子所属贴吧名称。
`like_count`	Yes	帖子获赞数。
`floor_count`	Yes	主题帖有效楼层数。
`reply_count`	Yes	帖子回复数。
`share_count`	Yes	帖子分享数。
`publish_time`	Yes	发帖时间，秒级 Unix 时间戳。
`collect_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
```
Changed30 schema fields changedNov 3, 2026
- addedOutput schema / properties / author / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / author / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / author / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / author / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / author / title
```
Added value: +"TiebaSearchAuthor"
```
- addedOutput schema / properties / collect_count / title
```
Added value: +"Collect Count"
```
- addedOutput schema / properties / content / title
```
Added value: +"Content"
```
- addedOutput schema / properties / floor_count / title
```
Added value: +"Floor Count"
```
- addedOutput schema / properties / forum_id / title
```
Added value: +"Forum Id"
```
- addedOutput schema / properties / forum_name / title
```
Added value: +"Forum Name"
```
- addedOutput schema / properties / images / items / properties / height / title
```
Added value: +"Height"
```
- addedOutput schema / properties / images / items / properties / url / title
```
Added value: +"Url"
```
- addedOutput schema / properties / images / items / properties / width / title
```
Added value: +"Width"
```
- addedOutput schema / properties / images / items / title
```
Added value: +"TiebaPostDetailImage"
```
- addedOutput schema / properties / images / title
```
Added value: +"Images"
```
- addedOutput schema / properties / like_count / title
```
Added value: +"Like Count"
```
- addedOutput schema / properties / post_url / title
```
Added value: +"Post Url"
```
- addedOutput schema / properties / publish_time / title
```
Added value: +"Publish Time"
```
- addedOutput schema / properties / reply_count / title
```
Added value: +"Reply Count"
```
- addedOutput schema / properties / share_count / title
```
Added value: +"Share Count"
```
- addedOutput schema / properties / thread_id / title
```
Added value: +"Thread Id"
```
- addedOutput schema / properties / title / title
```
Added value: +"Title"
```
- addedOutput schema / properties / videos / items / properties / cover_image_url / title
```
Added value: +"Cover Image Url"
```
- addedOutput schema / properties / videos / items / properties / duration_ms / title
```
Added value: +"Duration Ms"
```
- addedOutput schema / properties / videos / items / properties / height / title
```
Added value: +"Height"
```
- addedOutput schema / properties / videos / items / properties / video_url / title
```
Added value: +"Video Url"
```
- addedOutput schema / properties / videos / items / properties / width / title
```
Added value: +"Width"
```
- addedOutput schema / properties / videos / items / title
```
Added value: +"TiebaPostDetailVideo"
```
- addedOutput schema / properties / videos / title
```
Added value: +"Videos"
```
- addedOutput schema / title
```
Added value: +"TiebaPostDetailResult"
```
First observedOct 16, 2026

TDQS

B3.4/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 read-only, external-fetch nature is covered structurally. The description adds genuine value by disclosing that the result excludes the full reply list, but says nothing about rate limits, auth, or truncation behavior.

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?

A single front-loaded sentence with a semicolon-delimited scope caveat and no filler. It is tight, though the caveat could have been made more actionable by naming the alternative tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no explanation, and the single parameter is fully documented in the schema. Still, in a sibling set containing both a by_url variant and two comment tools, the description leaves the routing work to the agent rather than making the choice explicit.

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% and the schema itself already warns 不要传帖子链接 and explains where thread_id comes from. The description's only addition is reinforcing that the ID must be numeric, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource (读取百度贴吧详情, read Tieba thread detail) and pins the identifier type to a 数字 ID, which implicitly separates it from the sibling baidu_tieba_get_post_detail_by_url. It never names that sibling, so the differentiation requires the agent to infer it from the ID-type wording.

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

Usage Guidelines3/5

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

The clause 不包含完整回复列表 signals a boundary condition (this is not the tool for full reply lists), which implies the agent should look elsewhere for comments. However, it does not name baidu_tieba_get_post_comments_by_thread_id or state any positive when-to-use context, leaving routing 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?