Skip to main content
Glama

SocialDataX 知乎 Zhihu MCP

zhihu_search_suggestions

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": {
      "keyword": "<keyword>"
    },
    "name": "zhihu_search_suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes搜索关键词或短语;不要传链接、用户 ID 或 page_token。

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. Changed6 schema fields changed
    • addedOutput schema / properties / items / items / properties / icon_url / title
      Added value: +"Icon Url"
    • addedOutput schema / properties / items / items / properties / label / title
      Added value: +"Label"
    • addedOutput schema / properties / items / items / properties / text / title
      Added value: +"Text"
    • addedOutput schema / properties / items / items / title
      Added value: +"ZhihuSearchSuggestionItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / title
      Added value: +"ZhihuSearchSuggestionsResult"
  4. Added

TDQS

A4/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 safety and open-world behavior are covered. The description adds that the return is query suggestions rather than actual search results, which is useful, but says nothing about ranking, suggestion count limits, or failure modes for empty keywords.

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 short clauses, front-loaded with the positive capability followed by the exclusion. Nothing is wasted and there is no redundant restatement of the schema.

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?

With one required parameter, full schema coverage, annotations, and an output schema, the definition covers what an agent needs to call it correctly. The only minor gap is that the structure of the returned suggestions is left entirely to the output schema, which is acceptable here.

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 single keyword parameter is documented in the schema itself, including the negative constraint about links, user IDs, and page_tokens. The description only restates that a keyword is required, adding no format or length guidance beyond the schema.

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 specific verb-plus-resource: retrieve Zhihu search-box autocomplete suggestions from a keyword. It also explicitly negates the nearby sibling capabilities (searching users or content), so the agent can separate it from zhihu_search_content and zhihu_search_users without opening any schema.

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

Usage Guidelines4/5

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

The exclusion clause "不用于搜索用户或内容" tells the agent when not to use it and implicitly routes to the search siblings, but it does not name those siblings or state the positive use case (autocomplete/query expansion). Context is clear; explicit alternatives are only implied.

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