Skip to main content
Glama

SocialDataX 百度贴吧 MCP

baidu_tieba_search_suggestions

Read-only

获取贴吧搜索框的吧名联想词和相关贴吧信息,不搜索帖子或用户,不支持分页。

items 与 forums 为两组独立结果,不保证一一对应;可将 forums 中的 forum_name 传给 baidu_tieba_get_forum_detail 查询贴吧详情,或传给 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_suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes吧名关键词或前缀,例如 美食、旅行;不要传贴吧链接、帖子链接、ID 或分页令牌。

Output Schema

NameRequiredDescriptionDefault
itemsYes吧名联想词列表,保持返回顺序;无建议时为空数组。
forumsYes相关贴吧列表,保持返回顺序;与 items 不保证一一对应,无相关贴吧时为空数组。
pointsYes本次成功调用的积分消耗与账户积分余额。

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. Changed12 schema fields changed
    • addedOutput schema / properties / forums / items / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / forums / items / properties / forum_id / title
      Added value: +"Forum Id"
    • addedOutput schema / properties / forums / items / properties / forum_name / title
      Added value: +"Forum Name"
    • addedOutput schema / properties / forums / items / properties / forum_url / title
      Added value: +"Forum Url"
    • addedOutput schema / properties / forums / items / properties / member_count / title
      Added value: +"Member Count"
    • addedOutput schema / properties / forums / items / properties / slogan / title
      Added value: +"Slogan"
    • addedOutput schema / properties / forums / items / title
      Added value: +"TiebaSuggestedForum"
    • addedOutput schema / properties / forums / title
      Added value: +"Forums"
    • addedOutput schema / properties / items / items / properties / text / title
      Added value: +"Text"
    • addedOutput schema / properties / items / items / title
      Added value: +"TiebaSearchSuggestionItem"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / title
      Added value: +"TiebaSearchSuggestionsResult"
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover readOnly and openWorld, and the description adds real behavioral context beyond that: no pagination support, and the warning that items and forums are independent, non-corresponding result sets. It does not mention result limits or ordering, which keeps it short of 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.

Conciseness5/5

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

Two sentences, front-loaded with the capability and exclusions, followed by the result-shape caveat and sibling routing. Every clause carries either a constraint or a next-step pointer; nothing is padding.

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 one-parameter, read-only lookup with an output schema present, the description supplies the exclusions, the non-1:1 relationship between the two result groups, and the hand-off paths to sibling tools—enough for an agent to call it correctly without opening the schema.

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?

There is a single parameter with 100% schema description coverage; the schema already defines keyword as a forum-name keyword/prefix and already forbids links, IDs, and pagination tokens. The description adds no further meaning about the parameter, so the baseline of 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 concrete verb and resource, and the negative scope ("不搜索帖子或用户,不支持分页") explicitly separates it from the sibling search tools like baidu_tieba_search_posts and baidu_tieba_search_users.

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?

The description says both when to use it (getting forum-name suggestions from the search box) and when not to (posts, users, pagination), then names the concrete follow-up routes: forum_name into baidu_tieba_get_forum_detail or baidu_tieba_search_posts_in_forum.

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