SocialDataX 百度贴吧 Baidu Tieba MCP

baidu_tieba_get_post_comment_replies

Read-only

按主题帖 ID 和一级评论 ID 读取楼中楼回复，支持分页，不提供排序。

comment_id 取一级评论列表的 comment_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>",
      "comment_id": "<comment_id>"
    },
    "name": "baidu_tieba_get_post_comment_replies"
  }
}

Input Schema

Name	Required	Description
`thread_id`	Yes	主题帖数字 ID；使用查询一级评论时的 thread_id，也可取帖子搜索结果的 thread_id。
`comment_id`	Yes	一级评论 ID，取一级评论结果的 comment_id 或本工具结果的 parent_comment_id；不要传楼中楼回复自身的 comment_id。
`page_token`	No	分页令牌；首次留空，续页原样传入上一页 next_page_token，并保持 thread_id 和 comment_id 不变；不要使用搜索、一级评论或其它楼层的令牌。

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
```
Changed19 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 / 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 / parent_comment_id / title
```
Added value: +"Parent Comment Id"
```
- addedOutput schema / properties / items / items / properties / publish_time / title
```
Added value: +"Publish Time"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"TiebaCommentReplyItem"
```
- 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: +"TiebaCommentRepliesResult"
```
First observedOct 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two useful behavioral facts not in the annotations: pagination is supported and no sorting is offered, so the agent knows to iterate rather than sort. It stops short of describing reply volume or page sizes.

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 short sentences, front-loaded with the resource and required IDs, followed by the sourcing rule and the sibling pointer. No redundant restatement of the name or filler.

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 3-parameter read tool with an output schema and full schema coverage, the definition covers scope, pagination, ordering behavior, and where each ID comes from. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description earns above that by tying the two IDs to their source tools and warning against passing a reply's own comment_id. This adds workflow-level meaning beyond the schema's field notes.

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?

The opening clause states a specific verb and resource: read 楼中楼 (replies to a first-level comment) by thread post ID and first-level comment ID. It is immediately distinguishable from the sibling baidu_tieba_get_post_comments_by_thread_id, which it names as the tool for first-level comments.

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?

It explicitly routes the agent to the comment list tool for first-level comments and states that comment_id comes from that list, which is exactly the prerequisite needed before calling. It does not spell out broader when-not cases (e.g. when to stop paging or when replies are irrelevant), so it falls just short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SocialDataX 百度贴吧 Baidu Tieba 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?