SocialDataX 百度贴吧 MCP

baidu_tieba_get_user_posts_by_profile_url

Read-only

按主页链接读取该用户发布的主题帖，支持分页，不包含回复活动，不提供排序。

已有 profile_url 时优先使用本工具；仅有数字用户 ID 时使用 baidu_tieba_get_user_posts_by_user_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": {
      "profile_url": "<profile_url>"
    },
    "name": "baidu_tieba_get_user_posts_by_profile_url"
  }
}

Input Schema

Name	Required	Description	Default
`page_token`	No	分页令牌；首次留空，续页原样传入本接口返回的 next_page_token，并保持相同的用户入口和标识。不要使用搜索、评论或其他用户的令牌。
`profile_url`	Yes	百度贴吧用户主页完整链接，形如 https://tieba.baidu.com/home/main?id=…；可取搜索、详情或评论作者的 profile_url，不接受数字用户 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
```
Changed34 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: +"TiebaUserPostImage"
```
- 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 / reply_count / title
```
Added value: +"Reply Count"
```
- 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: +"TiebaUserPostVideo"
```
- addedOutput schema / properties / items / items / properties / videos / title
```
Added value: +"Videos"
```
- addedOutput schema / properties / items / items / properties / view_count / title
```
Added value: +"View Count"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"TiebaUserPostItem"
```
- 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: +"TiebaUserPostsResult"
```
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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds real behavioral facts: replies are excluded from the result set, sorting is not supported, completeness of lists and media is not guaranteed, and an empty token means the readable list ends. It stops short of describing rate limits, auth requirements, or expected result volume, which keeps it below a 5 for an open-world read tool.

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?

Three short sentences with zero waste: capability and exclusions first, tool routing second, reliability caveat and pagination termination last. The most decision-relevant information (what it does and which sibling to pick) is front-loaded.

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?

With an output schema available and read-only annotations present, the description needs only to cover scope, routing, and pagination termination — and it covers all three plus a completeness caveat. 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.

Parameters3/5

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

Schema description coverage is 100%, including the profile_url format and the page_token continuation rule, so the schema already does the parameter work. The description reinforces the entry-point choice ('已有 profile_url 时优先使用本工具') but adds no syntax or format detail beyond what the schema states.

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 first clause states a specific verb and resource ('读取该用户发布的主题帖' via profile link) and immediately bounds it ('不包含回复活动，不提供排序'). It also names the sibling that handles the other input type (baidu_tieba_get_user_posts_by_user_id), so an agent can separate this from the user_id variant without reading either schema.

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

Usage Guidelines5/5

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

Explicit routing rule: prefer this tool when profile_url is already available, use the user_id sibling otherwise. The description also states exclusions (no reply activity, no sorting) that would otherwise cause wrong tool selection, and the pagination expectation is carried both here and in the schema.

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?