Skip to main content
Glama

SocialDataX 百度贴吧 Baidu Tieba MCP

baidu_tieba_search_posts

Read-only

按搜索词搜索百度贴吧公开帖子,支持分页令牌和排序;需要综合搜索中的帖子顺序时使用综合搜索,指定帖子链接使用详情工具;需要限定贴吧时使用 baidu_tieba_search_posts_in_forum。图片、视频仅来自搜索结果,可能不完整。

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": {
      "keyword": "<keyword>"
    },
    "name": "baidu_tieba_search_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes搜索词或关键词短语,例如 方便面、旅行攻略;不要传帖子链接、帖子 ID 或分页令牌。需要限定某个贴吧时使用吧内帖子搜索。
sort_typeNo排序方式:newest 为最新、oldest 为最早、relevance 为相关。newest
page_tokenNo分页令牌;首次留空。续页将上一页完整 next_page_token 原样传回,并保持 keyword 与 sort_type 不变。

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. Changed32 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: +"TiebaSearchImage"
    • 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 / 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: +"TiebaSearchVideo"
    • addedOutput schema / properties / items / items / properties / videos / title
      Added value: +"Videos"
    • addedOutput schema / properties / items / items / title
      Added value: +"TiebaPostSearchItem"
    • 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: +"TiebaPostSearchResult"
  4. Changed3 schema fields changed
    • 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"
  5. First observed

TDQS

A4.3/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 a non-obvious data-quality caveat that images and videos come only from search results and may be incomplete, which is behavior an agent cannot infer from annotations. It does not discuss result volume, truncation, or rate limits, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then routing guidance, then the caveat — a sensible order with no filler sentences. The semicolon-chained single sentence is dense and slightly run-on, which costs a point against a cleaner multi-clause structure.

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 return-value explanation is unnecessary, and the description covers routing plus a media-completeness caveat. For a simple three-parameter read-only search this is nearly complete; only result-count or pagination-end behavior is unaddressed, which is minor.

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%, so keyword, sort_type, and page_token are already fully documented including the 'pass the previous next_page_token back unchanged' rule. The description only restates that pagination tokens and sorting are supported, adding no meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('按搜索词搜索百度贴吧公开帖子') plus scope (public posts only) and mentions pagination/sorting support. It also names the sibling that covers the adjacent case ('baidu_tieba_search_posts_in_forum'), so an agent can distinguish it from baidu_tieba_search_general, get_post_detail_by_url, and the in-forum search without opening any 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?

Explicitly routes three alternatives: use general search when you need post ordering from aggregate search, use the detail tool for a specific post link, and use baidu_tieba_search_posts_in_forum when a forum must be scoped. The alternatives are named by role rather than exact tool id in two cases, but the mapping to the sibling list is unambiguous.

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