Skip to main content
Glama

SocialDataX 知乎 Zhihu MCP

zhihu_get_hot_list

Read-only

读取知乎热榜,返回当前热榜问题标题、热度、回答数和问题链接。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zhihu_get_hot_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYes当前知乎热榜列表;当前不支持翻页。
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. Changed11 schema fields changed
    • addedOutput schema / properties / items / items / properties / answer_count / title
      Added value: +"Answer Count"
    • addedOutput schema / properties / items / items / properties / cover_image_url / title
      Added value: +"Cover Image Url"
    • addedOutput schema / properties / items / items / properties / hot_value / title
      Added value: +"Hot Value"
    • addedOutput schema / properties / items / items / properties / question_id / title
      Added value: +"Question Id"
    • addedOutput schema / properties / items / items / properties / question_url / title
      Added value: +"Question Url"
    • addedOutput schema / properties / items / items / properties / rank / title
      Added value: +"Rank"
    • addedOutput schema / properties / items / items / properties / summary / title
      Added value: +"Summary"
    • addedOutput schema / properties / items / items / properties / title / title
      Added value: +"Title"
    • addedOutput schema / properties / items / items / title
      Added value: +"ZhihuHotListItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / title
      Added value: +"ZhihuHotListResult"
  4. First observed

TDQS

A3.9/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 some value by naming the returned fields, but does not disclose freshness (live vs cached), rate limits, or list size, which are the traits an agent would actually need beyond the annotations.

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?

A single front-loaded sentence that states the act and then the payload, with no filler. It is efficient, though the list of return fields borders on restating what the output schema likely already provides.

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 zero-parameter read with an output schema and annotations already supplied, the description covers purpose and result shape sufficiently. Only freshness/size expectations are unaddressed, a minor gap given the structured fields carry the rest.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning for the description to clarify. The schema is fully closed (additionalProperties=false) and leaves nothing ambiguous.

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 states a specific verb-resource pair (读取知乎热榜) and enumerates the returned fields (标题、热度、回答数、问题链接). This is unmistakably different from siblings like zhihu_search_content or zhihu_get_content_detail_by_url, which target specific content rather than the platform-wide hot list.

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?

Usage is only implied: an agent can infer this is the tool for 'what is trending on Zhihu right now', but the description never states when to prefer it over zhihu_search_content or what it cannot do (e.g., historical hot lists, category filtering). With zero parameters there is little room for alternatives, which caps the harm.

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