Skip to main content
Glama

SocialDataX 好看视频 Haokan MCP

haokan_get_video_detail_by_url

Read-only

按页面链接读取好看视频详情、播放地址和作者摘要;只有视频 ID 时使用 haokan_get_video_detail_by_video_id。播放地址可能过期。

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": "haokan_get_video_detail_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes好看视频页面链接,格式为 https://haokan.baidu.com/v?vid=数字ID,可取视频搜索结果的 share_url。

Output Schema

NameRequiredDescriptionDefault
titleYes视频标题。
authorYes作者用户标识、主页链接、名称、头像与粉丝数量。
pointsYes本次成功调用的积分消耗与账户积分余额。
play_urlYes优先选取平台清晰度等级最高的非空播放地址,无候选时使用默认地址;均缺失时为 null,地址可能过期。
video_idYes好看视频 ID。
share_urlYes视频页面链接。
like_countYes平台返回的点赞数量;缺失时为 null。
view_countYes平台返回的播放次数;缺失时为 null。
publish_timeYes发布时间,Unix 秒级时间戳;不可用时为 null。
comment_countYes平台返回的评论数量;缺失时为 null。
cover_image_urlYes视频封面链接;不可用时为 null。
duration_secondsYes时长,单位秒;不可用时为 null。
playback_variantsYes按平台清晰度等级从高到低排列的非空播放地址,包含 quality、label、url;无候选时为空数组,非空时 play_url 等于第一项 url。

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. Changed22 schema fields changed
    • addedOutput schema / properties / author / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / author / properties / follower_count / title
      Added value: +"Follower Count"
    • 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: +"HaokanDetailAuthor"
    • addedOutput schema / properties / comment_count / title
      Added value: +"Comment Count"
    • addedOutput schema / properties / cover_image_url / title
      Added value: +"Cover Image Url"
    • addedOutput schema / properties / duration_seconds / title
      Added value: +"Duration Seconds"
    • addedOutput schema / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / play_url / title
      Added value: +"Play Url"
    • addedOutput schema / properties / playback_variants / items / properties / label / title
      Added value: +"Label"
    • addedOutput schema / properties / playback_variants / items / properties / quality / title
      Added value: +"Quality"
    • addedOutput schema / properties / playback_variants / items / properties / url / title
      Added value: +"Url"
    • addedOutput schema / properties / playback_variants / items / title
      Added value: +"HaokanPlaybackVariant"
    • addedOutput schema / properties / playback_variants / title
      Added value: +"Playback Variants"
    • addedOutput schema / properties / publish_time / title
      Added value: +"Publish Time"
    • addedOutput schema / properties / share_url / title
      Added value: +"Share Url"
    • addedOutput schema / properties / title / title
      Added value: +"Title"
    • addedOutput schema / properties / video_id / title
      Added value: +"Video Id"
    • addedOutput schema / properties / view_count / title
      Added value: +"View Count"
    • addedOutput schema / title
      Added value: +"HaokanVideoDetailResult"
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds useful behavior beyond the readOnlyHint/openWorldHint annotations: it says the playback address may expire, which tells the agent not to cache or reuse it. It does not describe rate limits, failure modes for dead links, or region restrictions, so it stops short of full transparency.

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?

One compact sentence plus one caveat clause, with the output contents and the disambiguation rule front-loaded and zero filler. Every clause adds information an agent needs.

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?

Because an output schema exists, return values do not need explaining, and the description covers input form, sibling routing, and the expiry caveat. It is close to complete for a single-parameter read tool, with only edge-case failure behavior omitted.

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 schema description already specifies the URL format and mentions share_url as a source, so the description adds no parameter meaning beyond the schema. A baseline 3 is appropriate here.

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 uses a specific verb and resource ("读取好看视频详情、播放地址和作者摘要") and names the sibling it is not (haokan_get_video_detail_by_video_id). An agent can distinguish this URL-based variant from the ID-based one without opening either 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?

It gives an explicit selection rule: use this tool when you have a page link, and switch to haokan_get_video_detail_by_video_id when you only have a video ID. The condition and the alternative are both stated.

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