SocialDataX 百度贴吧 MCP

baidu_tieba_get_post_comments_by_url

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": {
      "url": "<url>"
    },
    "name": "baidu_tieba_get_post_comments_by_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	百度贴吧主题帖完整链接，可取搜索结果的 post_url，支持 /p/数字ID/；不要传纯 ID。
`sort_type`	No	评论排序请求：hot 请求热门评论（默认），newest 请求最新评论，oldest 请求最早评论；实际返回顺序以贴吧为准。	hot
`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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that only first-level comments are returned and 楼中楼 replies are excluded — but says nothing about ordering caveats, rate limits, or result volume, and the output schema is left to describe the return shape.

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?

A single compact sentence front-loads the resource and the scope constraint with no filler. Every clause (URL-based, first-level only, sorting, pagination, exclusion) carries information.

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?

With an output schema present and full schema parameter coverage, the description only needs to establish scope and routing, which it does. The remaining gap is minor: it does not point explicitly at the replies or thread_id siblings for the cases it excludes.

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 each parameter (url, sort_type, page_token) has its own detailed description including format constraints and the pagination contract. The description only generically mentions '支持排序和分页', adding no meaning beyond the schema, so the 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 names a specific verb and resource ('读取一级评论' from a 主题帖链接) and states the scope precisely, including the explicit exclusion of 楼中楼 replies, which separates it from the replies sibling. It does not explicitly name the URL-vs-thread_id sibling as an alternative, leaving that differentiation mostly to the tool name.

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 exclusion of nested replies implies that a different tool should be used for those, and the mention of sorting/pagination hints at the expected call pattern. However, there is no explicit 'use this when / use X instead' statement, and prerequisites such as needing a full post URL are only stated in the schema, not the description.

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?