Skip to main content
Glama

SocialDataX 百度贴吧 MCP

baidu_tieba_get_post_detail_by_url

Read-only

按百度贴吧主题帖链接读取详情;不包含完整回复列表。

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": {
      "url": "<url>"
    },
    "name": "baidu_tieba_get_post_detail_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes百度贴吧主题帖完整链接,支持 /p/数字ID/;不要传纯 ID。

Output Schema

NameRequiredDescriptionDefault
titleYes帖子标题。
authorYes帖子作者。
imagesYes首楼图片列表。
pointsYes本次成功调用的积分消耗与账户积分余额。
videosYes首楼视频列表。
contentYes首楼正文纯文本;表情以“[表情]”表示;无可见正文时为空字符串。
forum_idYes所属贴吧 ID,以字符串表示。
post_urlYes帖子页面链接。
thread_idYes主题帖 ID,以字符串表示。
forum_nameYes帖子所属贴吧名称。
like_countYes帖子获赞数。
floor_countYes主题帖有效楼层数。
reply_countYes帖子回复数。
share_countYes帖子分享数。
publish_timeYes发帖时间,秒级 Unix 时间戳。
collect_countYes帖子收藏数。

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. Changed30 schema fields changed
    • addedOutput schema / properties / author / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / author / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / author / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / author / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / author / title
      Added value: +"TiebaSearchAuthor"
    • addedOutput schema / properties / collect_count / title
      Added value: +"Collect Count"
    • addedOutput schema / properties / content / title
      Added value: +"Content"
    • addedOutput schema / properties / floor_count / title
      Added value: +"Floor Count"
    • addedOutput schema / properties / forum_id / title
      Added value: +"Forum Id"
    • addedOutput schema / properties / forum_name / title
      Added value: +"Forum Name"
    • addedOutput schema / properties / images / items / properties / height / title
      Added value: +"Height"
    • addedOutput schema / properties / images / items / properties / url / title
      Added value: +"Url"
    • addedOutput schema / properties / images / items / properties / width / title
      Added value: +"Width"
    • addedOutput schema / properties / images / items / title
      Added value: +"TiebaPostDetailImage"
    • addedOutput schema / properties / images / title
      Added value: +"Images"
    • addedOutput schema / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / post_url / title
      Added value: +"Post Url"
    • addedOutput schema / properties / publish_time / title
      Added value: +"Publish Time"
    • addedOutput schema / properties / reply_count / title
      Added value: +"Reply Count"
    • addedOutput schema / properties / share_count / title
      Added value: +"Share Count"
    • addedOutput schema / properties / thread_id / title
      Added value: +"Thread Id"
    • addedOutput schema / properties / title / title
      Added value: +"Title"
    • addedOutput schema / properties / videos / items / properties / cover_image_url / title
      Added value: +"Cover Image Url"
    • addedOutput schema / properties / videos / items / properties / duration_ms / title
      Added value: +"Duration Ms"
    • addedOutput schema / properties / videos / items / properties / height / title
      Added value: +"Height"
    • addedOutput schema / properties / videos / items / properties / video_url / title
      Added value: +"Video Url"
    • addedOutput schema / properties / videos / items / properties / width / title
      Added value: +"Width"
    • addedOutput schema / properties / videos / items / title
      Added value: +"TiebaPostDetailVideo"
    • addedOutput schema / properties / videos / title
      Added value: +"Videos"
    • addedOutput schema / title
      Added value: +"TiebaPostDetailResult"
  4. First observed

TDQS

A3.5/5.0
Behavior3/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 structurally. The description adds a useful scope boundary — no full reply list — which prevents an agent from expecting thread content, but it says nothing about failure modes for invalid or deleted links, or about openWorld variability.

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?

Two short clauses, with the core action front-loaded and the scope exclusion appended. Nothing is wasted, though the brevity leaves the sibling routing implicit.

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?

For a one-parameter read tool with annotations and an output schema, the definition covers the essential action and its main limitation. The remaining gap is routing against the by_thread_id and comment tools, which an agent must infer from the tool names alone.

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?

With a single parameter at 100% schema description coverage, the schema already documents the format, the https?:// pattern, and the warning against passing a bare ID. The description only reinforces that the input is a link, adding no syntax or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 constrains the input form to a link (按…链接), which implicitly separates it from the by_thread_id sibling. It does not explicitly name the ID-based variant or the comment siblings, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Saying it does not include the full reply list hints that comment tools should be used when replies are needed, but it never names baidu_tieba_get_post_comments_by_url or the other reply tools, and gives no explicit when-to-use statement. Usage is implied rather than directed.

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