Skip to main content
Glama

SocialDataX 百度贴吧 MCP

baidu_tieba_get_forum_detail

Read-only

按准确吧名获取贴吧简介、标语、建吧日期、关注人数、帖子统计和友情链接贴吧。

不知道准确吧名时,先用 baidu_tieba_search_suggestions 获取 forum_name; 按关键词查找吧内帖子时,使用 baidu_tieba_search_posts_in_forum;无需关键词浏览时使用 baidu_tieba_get_forum_posts。

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_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
forum_nameYes准确贴吧名称,例如 方便面;直接使用结果中的 forum_name,不要自行追加“吧”字;不要传 URL 或数字 ID,无需 URL 编码。

Output Schema

NameRequiredDescriptionDefault
pointsYes本次成功调用的积分消耗与账户积分余额。
sloganYes贴吧标语;未提供内容时返回空字符串。
forum_urlYes贴吧链接。
forum_nameYes查询的贴吧名称。
post_countYes贴吧展示的帖子统计数,不保证仅统计主题帖。
descriptionYes贴吧简介;未提供内容时返回空字符串。
created_dateYes建吧日期,格式 YYYY-MM-DD。
member_countYes关注人数。
related_forumsYes贴吧展示的友情链接列表,保留展示顺序,不代表算法相似度排名;无友情链接时为空数组。

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. Changed14 schema fields changed
    • addedOutput schema / properties / created_date / title
      Added value: +"Created Date"
    • addedOutput schema / properties / description / title
      Added value: +"Description"
    • addedOutput schema / properties / forum_name / title
      Added value: +"Forum Name"
    • addedOutput schema / properties / forum_url / title
      Added value: +"Forum Url"
    • addedOutput schema / properties / member_count / title
      Added value: +"Member Count"
    • addedOutput schema / properties / post_count / title
      Added value: +"Post Count"
    • addedOutput schema / properties / related_forums / items / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / related_forums / items / properties / forum_id / title
      Added value: +"Forum Id"
    • addedOutput schema / properties / related_forums / items / properties / forum_name / title
      Added value: +"Forum Name"
    • addedOutput schema / properties / related_forums / items / properties / forum_url / title
      Added value: +"Forum Url"
    • addedOutput schema / properties / related_forums / items / title
      Added value: +"TiebaRelatedForum"
    • addedOutput schema / properties / related_forums / title
      Added value: +"Related Forums"
    • addedOutput schema / properties / slogan / title
      Added value: +"Slogan"
    • addedOutput schema / title
      Added value: +"TiebaForumDetailResult"
  4. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already tell the agent that this is a safe read of external data. The description reinforces the strict input requirement (an exact forum name, not a URL or numeric ID), which is useful, but it does not discuss failure behavior when the name is wrong, coverage limits, or freshness.

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?

The description front-loads the capability sentence and puts fallback routing in a compact second paragraph. The field enumeration in the first sentence is slightly list-like, but every item signals what the result contains, so the description stays tight overall.

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 the description does not need to explain return values, and the single parameter is fully specified. Its main remaining gap is what happens when the exact forum name is wrong or ambiguous, but that is partly covered by the search_suggestions pointer.

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 coverage is 100%, and the forum_name property already documents the 'do not append 吧', 'no URL or numeric ID', and 'no URL encoding' rules. The description mostly restates the accuracy constraint and adds the escape hatch to search_suggestions, so a baseline 3 is appropriate.

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 names a specific verb and resource (按准确吧名获取贴吧...) and enumerates what is fetched: 简介、标语、建吧日期、关注人数、帖子统计、友情链接贴吧. This clearly distinguishes it from the post-listing and post-search siblings, which are named explicitly.

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 rules are given for three cases: when the exact forum name is unknown, use baidu_tieba_search_suggestions; for keyword search inside a forum, use baidu_tieba_search_posts_in_forum; for keyword-free browsing, use baidu_tieba_get_forum_posts. The agent does not need to infer competition between siblings.

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