Skip to main content
Glama

SocialDataX 百度贴吧 Baidu Tieba MCP

baidu_tieba_get_forum_posts

Read-only

按准确吧名浏览普通帖和置顶帖,无需关键词,支持分页,支持排序或仅查看精华帖。

精华帖仅支持默认顺序,不提供分类选项。按关键词查找吧内帖子使用 baidu_tieba_search_posts_in_forum; 只查询贴吧简介和统计使用 baidu_tieba_get_forum_detail。摘要和媒体可能不完整。

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": {
      "forum_name": "<forum_name>"
    },
    "name": "baidu_tieba_get_forum_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sort_typeNo排序方式:default 为贴吧默认顺序,newest 为最新发布,latest_reply 为最近回复,hot 为热门。顺序以贴吧实际返回为准,不保证严格按时间排列;仅查看精华时只支持 default。default
forum_nameYes准确贴吧名称,例如 方便面;直接使用结果中的 forum_name,不要自行追加“吧”字;不要传 URL 或数字 ID,无需 URL 编码。
page_tokenNo分页令牌;首次留空,续页原样传回 next_page_token,并保持 forum_name、sort_type、featured_only 不变。切换排序或精华筛选时,将 page_token 留空重新查询。只根据令牌判断是否续页,不按条数判断;不要使用其他接口或其他贴吧的令牌。
featured_onlyNo是否仅查看精华帖,false 表示不筛选(仍可包含精华帖);true 时 sort_type 必须为 default,按贴吧精华列表顺序返回。

Output Schema

NameRequiredDescriptionDefault
itemsYes本次返回的普通帖和置顶帖,保留展示顺序;不保证跨页无重复或覆盖全吧历史帖子。
pointsYes本次成功调用的积分消耗与账户积分余额。
next_page_tokenYes下一页令牌;为空表示本次可读取列表结束。是否续页只看令牌,不按返回条数判断。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed35 schema fields changed
    • 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: +"TiebaForumPostImage"
    • addedOutput schema / properties / items / items / properties / images / title
      Added value: +"Images"
    • addedOutput schema / properties / items / items / properties / is_pinned / title
      Added value: +"Is Pinned"
    • 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: +"TiebaForumPostItem"
    • 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: +"TiebaForumPostsResult"
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the read-only and open-world annotations, it discloses that summaries and media may be incomplete, an important data-fidelity caveat. It also describes result-scope and featured-list limitations, though most detailed pagination and ordering behavior is left to the schema.

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?

The description is compact and front-loaded with the core purpose and capabilities. Its remaining sentences efficiently cover constraints, sibling alternatives, and an output-quality caveat without redundant explanation.

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?

Together with the fully documented input schema and available output schema, the description supplies everything needed to select and invoke the tool correctly. Tool selection, key constraints, alternatives, and result limitations are all addressed.

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 already thoroughly documents the exact forum name, sort values, token lifecycle, and featured-only constraint. The description reinforces the exact-name requirement and default-order restriction but adds little parameter meaning beyond those structured fields.

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 description clearly states the action, resource, and scope: browsing ordinary and pinned posts by exact forum name, without keywords. It also distinguishes this tool from the in-forum keyword search and forum-detail siblings.

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?

It gives explicit routing guidance: use baidu_tieba_search_posts_in_forum for keyword searches and baidu_tieba_get_forum_detail for forum introductions and statistics. The featured-post restriction to default ordering and lack of category options further clarify when and how this tool can be used.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources