Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_search_finder_user

Read-only

按关键词或视频号 ID 查找微信视频号用户,支持 page_token 分页;返回的 user_id 可用于查询用户资料和发布作品。已有 user_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": {
      "keyword": "<keyword>"
    },
    "name": "wechat_search_finder_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes视频号用户名称、关键词或视频号 ID;不要传作品链接或分页令牌。
page_tokenNo首次留空;续页原样传入同一用户搜索返回的 next_page_token,并保持 keyword 不变。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页视频号用户列表。
pointsYes本次成功调用的积分消耗与账户积分余额。
next_page_tokenYes下一页分页令牌;为空表示结束。

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. Changed8 schema fields changed
    • addedOutput schema / properties / items / items / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / items / items / properties / bio / title
      Added value: +"Bio"
    • addedOutput schema / properties / items / items / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / items / items / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / items / items / title
      Added value: +"WechatUserSearchItemData"
    • 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: +"WechatUserSearchResult"
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds behavior beyond that: results are paginated via page_token, and the returned user_id is a handoff key for the profile and posted-video tools. It does not discuss rate limits or result caps, but the output schema covers the return shape.

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?

There are only two dense clauses with zero filler: the capability and its pagination come first, then the routing guidance and the exclusions. Every phrase carries either scope or routing information.

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 two-parameter search tool, the description is complete: it identifies the search entry point, explains how results feed downstream tool calls, and marks the boundaries. Because the annotations and the output schema carry the safety and return-value burdens, only minor operational details such as result caps are absent.

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 the schema itself already explains that keyword accepts a name, keyword, or 视频号 ID and must not be a work link or page token, and that page_token must be echoed unchanged from the previous next_page_token. The description restates the keyword and pagination roles without adding format or syntax detail beyond the schema, so the baseline 3 applies.

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 sentence states a specific action on a specific resource: finding WeChat Channels (视频号) users by keyword or account ID. It also names what it is not, namely WeChat contacts or official accounts (公众号), and thereby separates it from the sibling search tools such as wechat_search_mp_articles and wechat_search_videos.

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 explicitly covers the alternative route: when a user_id or a work link is already known, use the user-profile tool directly instead of this one. The exclusion of contacts and 公众号 further defines the boundary, so the agent has an explicit when, a when-not, and a named alternative.

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