SocialDataX 百度贴吧 MCP

baidu_tieba_get_post_comments_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_comments_by_thread_id"
  }
}

Input Schema

Name	Required	Description	Default
`sort_type`	No	评论排序请求：hot 请求热门评论（默认），newest 请求最新评论，oldest 请求最早评论；实际返回顺序以贴吧为准。	hot
`thread_id`	Yes	主题帖数字 ID，可取搜索结果的 thread_id；不要传帖子链接。
`page_token`	No	分页令牌；首次留空。续页将上一页完整 next_page_token 原样传回，并保持同一帖子与 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
```
Changed21 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: +"TiebaCommentAuthor"
```
- addedOutput schema / properties / items / items / properties / comment_id / title
```
Added value: +"Comment Id"
```
- addedOutput schema / properties / items / items / properties / content / title
```
Added value: +"Content"
```
- addedOutput schema / properties / items / items / properties / floor / title
```
Added value: +"Floor"
```
- addedOutput schema / properties / items / items / properties / has_replies / title
```
Added value: +"Has Replies"
```
- addedOutput schema / properties / items / items / properties / ip_location / title
```
Added value: +"Ip Location"
```
- addedOutput schema / properties / items / items / properties / like_count / title
```
Added value: +"Like Count"
```
- addedOutput schema / properties / items / items / properties / mentioned_users / items / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / items / items / properties / mentioned_users / items / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / items / items / properties / mentioned_users / items / title
```
Added value: +"TiebaMentionedUser"
```
- addedOutput schema / properties / items / items / properties / mentioned_users / title
```
Added value: +"Mentioned Users"
```
- addedOutput schema / properties / items / items / properties / publish_time / title
```
Added value: +"Publish Time"
```
- addedOutput schema / properties / items / items / properties / reply_count / title
```
Added value: +"Reply Count"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"TiebaCommentItem"
```
- 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: +"TiebaCommentsResult"
```
First observedOct 16, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Read-only annotations already declare that this is a safe read. The description adds one behavioral fact: that the tool returns only first-level (top-level) comments and skips nested replies. It says nothing further about rate limits or result volume, and the order caveat lives in the schema, not the description.

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?

This is a single tight sentence: the resource and ID type come first, and then the capability and the scope exclusion follow. No filler remains.

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 the return values need no explanation. For a three-parameter read tool, the description covers the input mode, the supported features, and the key result boundary (top-level comments only), which is sufficient for correct invocation.

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%, so the thread_id, sort_type, and page_token semantics are already documented in detail. The description only restates that sorting and pagination are supported, adding no new hints such as token reuse rules that the schema does not already carry.

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 names a specific action and resource ('按主题帖数字 ID 读取百度贴吧一级评论') and states the scope of the result. The phrase '不包含楼中楼回复' implicitly tells the agent how it differs from the sibling baidu_tieba_get_post_comment_replies, even though no sibling is named directly.

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?

Usage is only implied: the description says to call it with a numeric thread ID, and it rules out nested replies. It never says when to prefer this tool over baidu_tieba_get_post_comments_by_url or when to switch to the replies tool.

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?