SocialDataX 知乎 Zhihu MCP

zhihu_search_content

Read-only

按搜索词搜索知乎公开内容。用户需要按搜索词查找内容时使用；已有回答页、专栏文章页或独立视频页链接且需要详情或评论时使用对应 URL 工具；已有用户主页链接时使用用户资料或文章列表工具；支持类型、排序、发布时间筛选与 page_token 翻页。

Input Schema

Name	Required	Description	Default
`keyword`	Yes	知乎内容搜索词，可传关键词或短语，例如问题、话题、人物、机构或内容需求；不要传问题链接、回答链接、专栏文章链接、视频链接、用户主页链接或 page_token。
`sort_type`	No	排序方式：general=综合排序，upvote_count_descending=最多赞同，time_descending=最新发布。如无明确排序需求，保持 general。	general
`page_token`	No	知乎搜索分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一关键词、同一类型筛选、同一排序和同一发布时间筛选链路。更换关键词、类型、排序或发布时间筛选时，请清空 page_token 后从第一页重新搜索。
`content_type`	No	内容类型筛选：all=不限类型，answer=只看回答，article=只看文章，video=只看视频内容（可能返回独立视频 video 或带视频的回答 videoanswer；videoanswer 不是独立视频，也不是筛选取值）。	all
`publish_time_range`	No	发布时间筛选：all=不限时间，day=一天内，week=一周内，month=一月内，three_months=三月内，half_year=半年内，year=一年内。如无明确筛选需求，保持 all。独立视频综合排序的 day/week 按更新时间筛选，可能包含较早发布的视频；发布时间和更新时间分别见返回的 publish_time、update_time。	all

Output Schema

Name	Required	Description
`items`	Yes	当前页知乎内容列表；当前页可能为空，是否可继续翻页以 next_page_token 是否为空为准。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`next_page_token`	Yes	下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；只用于当前搜索续页；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / publish_time_range / description

Previous value: -"发布时间筛选：all=不限时间，day=一天内，week=一周内，month=一月内，three_months=三月内，half_year=半年内，year=一年内。如无明确筛选需求，保持 all。"New value: +"发布时间筛选：all=不限时间，day=一天内，week=一周内，month=一月内，three_months=三月内，half_year=半年内，year=一年内。如无明确筛选需求，保持 all。独立视频综合排序的 day/week 按更新时间筛选，可能包含较早发布的视频；发布时间和更新时间分别见返回的 publish_time、update_time。"

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```

Changed29 schema fields changedNov 3, 2026

changedOutput schema / properties / items / items / properties / answer / anyOf

Previous value: -[
-  {
-    "properties": {
-      "visit_count": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "回答访问数；不是文章阅读数或视频播放数；不可用时为 null。"
-      }
-    },
-    "required": [
-      "visit_count"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "visit_count": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "回答访问数；不是文章阅读数或视频播放数；不可用时为 null。",
+        "title": "Visit Count"
+      }
+    },
+    "required": [
+      "visit_count"
+    ],
+    "title": "ZhihuAnswerSummaryData",
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
addedOutput schema / properties / items / items / properties / author / properties / bio / title
```
Added value: +"Bio"
```
addedOutput schema / properties / items / items / properties / author / properties / follower_count / title
```
Added value: +"Follower Count"
```
addedOutput schema / properties / items / items / properties / author / properties / name / title
```
Added value: +"Name"
```
addedOutput schema / properties / items / items / properties / author / properties / profile_url / title
```
Added value: +"Profile Url"
```
addedOutput schema / properties / items / items / properties / author / properties / received_upvote_count / title
```
Added value: +"Received Upvote Count"
```
addedOutput schema / properties / items / items / properties / author / properties / user_id / title
```
Added value: +"User Id"
```
addedOutput schema / properties / items / items / properties / author / properties / verification_label / title
```
Added value: +"Verification Label"
```
addedOutput schema / properties / items / items / properties / author / properties / verified / title
```
Added value: +"Verified"
```
addedOutput schema / properties / items / items / properties / author / title
```
Added value: +"ZhihuAuthorSummaryData"
```
addedOutput schema / properties / items / items / properties / collect_count / title
```
Added value: +"Collect Count"
```
addedOutput schema / properties / items / items / properties / comment_count / title
```
Added value: +"Comment Count"
```
addedOutput schema / properties / items / items / properties / content_id / title
```
Added value: +"Content Id"
```
addedOutput schema / properties / items / items / properties / content_type / title
```
Added value: +"Content Type"
```
addedOutput schema / properties / items / items / properties / content_url / title
```
Added value: +"Content Url"
```
addedOutput schema / properties / items / items / properties / cover_image_url / title
```
Added value: +"Cover Image Url"
```
addedOutput schema / properties / items / items / properties / image_urls / title
```
Added value: +"Image Urls"
```
addedOutput schema / properties / items / items / properties / publish_time / title
```
Added value: +"Publish Time"
```

changedOutput schema / properties / items / items / properties / question / anyOf

Previous value: -[
-  {
-    "properties": {
-      "question_id": {
-        "description": "知乎问题 ID；用于按问题聚合回答，不是内容详情或评论输入；不可用时为空字符串。",
-        "type": "string"
-      },
-      "question_url": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "知乎问题页面链接；不是内容详情或评论请求的 content_url；不可用时为 null。"
-      },
-      "title": {
-        "description": "问题标题；不可用时为空字符串。",
-        "type": "string"
-      }
-    },
-    "required": [
-      "question_id",
-      "title",
-      "question_url"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "question_id": {
+        "description": "知乎问题 ID；用于按问题聚合回答，不是内容详情或评论输入；不可用时为空字符串。",
+        "title": "Question Id",
+        "type": "string"
+      },
+      "question_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "知乎问题页面链接；不是内容详情或评论请求的 content_url；不可用时为 null。",
+        "title": "Question Url"
+      },
+      "title": {
+        "description": "问题标题；不可用时为空字符串。",
+        "title": "Title",
+        "type": "string"
+      }
+    },
+    "required": [
+      "question_id",
+      "title",
+      "question_url"
+    ],
+    "title": "ZhihuQuestionSummaryData",
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

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 / properties / update_time / title
```
Added value: +"Update Time"
```
addedOutput schema / properties / items / items / properties / upvote_count / title
```
Added value: +"Upvote Count"
```

changedOutput schema / properties / items / items / properties / video / anyOf

Previous value: -[
-  {
-    "properties": {
-      "duration_ms": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "视频时长，毫秒；不可用时为 null。"
-      },
-      "play_count": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "视频播放数；不可用时为 null。"
-      }
-    },
-    "required": [
-      "duration_ms",
-      "play_count"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "duration_ms": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频时长，毫秒；不可用时为 null。",
+        "title": "Duration Ms"
+      },
+      "play_count": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频播放数；不可用时为 null。",
+        "title": "Play Count"
+      }
+    },
+    "required": [
+      "duration_ms",
+      "play_count"
+    ],
+    "title": "ZhihuSearchVideoSummaryData",
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / items / items / title
```
Added value: +"ZhihuContentSearchItemData"
```
addedOutput schema / properties / items / title
```
Added value: +"Items"
```
addedOutput schema / properties / next_page_token / title
```
Added value: +"Next Page Token"
```

addedOutput schema / title

Added value: +"ZhihuContentSearchResult"

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds that scope is public Zhihu content only and that results are paginated via page_token. It does not mention quota, rate limits, or result-set size, but the essentials beyond the annotations are present.

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?

One dense but well-ordered passage: purpose first, then routing to alternatives, then capability summary. Every clause carries information, though the semicolon-chained Chinese phrasing packs three distinct jobs into a single block rather than separating them.

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 five-parameter search tool with a full output schema and complete param documentation, the description covers purpose, routing, and filter/pagination capability, which is enough for correct invocation. Minor omissions like result volume or whether snippets are returned are acceptable given the output schema exists.

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 description coverage is 100%, so all five parameters and their enums are already fully documented, including the page_token reuse rules. The description only summarizes the available filter dimensions (type, sort, publish time, pagination) without adding syntax or format meaning beyond the schema, which is the baseline case.

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?

Opens with a specific verb+resource ("按搜索词搜索知乎公开内容") and immediately scopes it to keyword-driven content search. It is distinguishable from every sibling because it names the URL-based detail/comment tools and the user-profile tools as the alternatives for non-keyword inputs.

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?

States the triggering condition (user wants to find content by search term) and then explicitly routes away three other cases: existing answer/article/video links, and existing profile links. This is an explicit when-to-use / when-not-to-use map with named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SocialDataX 知乎 Zhihu MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?