Skip to main content
Glama

SocialDataX 微信 WeChat MCP

by com.52choujiang
OverviewDiscussionsAdmin

wechat_search_videos

Read-only

按搜索词搜索微信视频号视频，当前仅返回视频、不返回图文。用户需要按搜索词查找视频时使用；已有作品链接时直接使用详情或评论工具；已有合法 encrypted_object_id 时直接使用按 ID 详情或口播转文字工具，均无需先调用搜索；支持 sort_type、duration_range 和 page_token 翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes微信视频号视频搜索词；只传关键词或短语；不要传任何链接、encrypted_object_id、user_id 或 page_token 作为 keyword。
sort_typeNo搜索排序方式，可选：all（不限，默认）、time_descending（最新）、collect_count_descending（最热/最多收藏排序）。如无明确排序需求，保持 all。all
page_tokenNopage_token 是不透明分页令牌。首次请求留空；继续翻页时必须将上一次返回的完整 next_page_token 原样传入，作为 page_token 使用；只能用于同一微信视频号搜索分页链路、同一关键词和同一筛选条件的下一页，不能跨能力、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。
duration_rangeNo视频时长筛选，可选：all（不限，默认）、under_5_min（5 分钟以下）、between_5_and_20_min（5-20 分钟）、over_20_min（20 分钟以上）。如无明确筛选需求，保持 all。all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页搜索结果中的视频列表，已过滤直播、合集和相关搜索卡片；当前页过滤后可能为空数组
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
next_page_tokenYes下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；next_page_token 只能用于同一微信视频号搜索分页链路；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"微信视频号搜索关键词；视频搜索自然语言关键词例如 露营、周末带娃、品牌名或内容需求；不要传视频链接、公众号文章链接、用户主页链接、encrypted_object_id、user_id 或 page_token 作为 keyword。"New value: +"微信视频号视频搜索词；只传关键词或短语；不要传任何链接、encrypted_object_id、user_id 或 page_token 作为 keyword。"
  2. Changed2 schema fields changed
    • addedOutput schema / properties / points
      Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "points"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"微信视频号搜索关键词，例如 露营、周末带娃；不要传链接或分页 token。"New value: +"微信视频号搜索关键词；视频搜索自然语言关键词例如 露营、周末带娃、品牌名或内容需求；不要传视频链接、公众号文章链接、用户主页链接、encrypted_object_id、user_id 或 page_token 作为 keyword。"
  4. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / topic_tags
      Added value: +{
+  "description": "作品文案中的话题标签；无话题时为空数组；每项只返回 name",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "description": "话题标签名称",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "encrypted_object_id",
-  "content_type",
-  "description",
-  "cover_image_url",
-  "publish_time",
-  "duration_seconds",
-  "like_count",
-  "collect_count",
-  "comment_count",
-  "share_count",
-  "author"
-]New value: +[
+  "encrypted_object_id",
+  "content_type",
+  "description",
+  "topic_tags",
+  "cover_image_url",
+  "publish_time",
+  "duration_seconds",
+  "like_count",
+  "collect_count",
+  "comment_count",
+  "share_count",
+  "author"
+]
  5. Changed3 schema fields changed
    • changedInput schema / properties / sort_type / default
      Previous value: -"general"New value: +"all"
    • changedInput schema / properties / sort_type / description
      Previous value: -"搜索排序方式，可选：general（综合排序，默认）、time_descending（最新）、popularity_descending（热度排序）。如无明确排序需求，保持 general。"New value: +"搜索排序方式，可选：all（不限，默认）、time_descending（最新）、collect_count_descending（最热/最多收藏排序）。如无明确排序需求，保持 all。"
    • changedInput schema / properties / sort_type / enum
      Previous value: -[
-  "general",
-  "time_descending",
-  "popularity_descending"
-]New value: +[
+  "all",
+  "time_descending",
+  "collect_count_descending"
+]
  6. Changed3 schema fields changed
    • changedInput schema / properties / sort_type / default
      Previous value: -"all"New value: +"general"
    • changedInput schema / properties / sort_type / description
      Previous value: -"搜索排序方式，可选：all（不限，默认）、latest（最新）、popular（最热）。如无明确排序需求，保持 all。"New value: +"搜索排序方式，可选：general（综合排序，默认）、time_descending（最新）、popularity_descending（热度排序）。如无明确排序需求，保持 general。"
    • changedInput schema / properties / sort_type / enum
      Previous value: -[
-  "all",
-  "latest",
-  "popular"
-]New value: +[
+  "general",
+  "time_descending",
+  "popularity_descending"
+]
  7. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already signal readOnlyHint and openWorldHint; the description adds meaningful scope behavior: it currently returns videos but not image-text posts, and supports pagination via page_token. It does not go into rate limits or failure modes, but for a read-only search tool this is adequate.

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?

The description is a single dense paragraph front-loaded with the core action and scope, followed by usage routing and parameter support. Every clause adds value; no filler or restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a filtered search tool with an output schema, the description is complete: it states the trigger condition, the alternative paths, the scope limitation, and the available controls (sort_type, duration_range, page_token pagination). Nothing needed to select and call it correctly is missing.

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%, and each parameter has a detailed description, so the tool description only needs to mention that sort_type, duration_range, and page_token are supported. It adds no syntax beyond the schema, matching the baseline for full schema coverage.

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?

Description opens with a clear verb and resource: '按搜索词搜索微信视频号视频' (search WeChat Channels videos by keyword). It also differentiates itself from siblings by noting it returns only videos, not image-text posts, and contrasts with detail/comment/speech-text tools.

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?

Explicitly states when to use ('用户需要按搜索词查找视频时使用') and when not to: if a work link or valid encrypted_object_id is already available, use detail/comment or ID-based speech-text tools directly, '均无需先调用搜索'. This gives clear routing versus the many sibling tools.

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

All SocialDataX 微信 WeChat MCP toolsInspect
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