Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_get_hot_search_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": "wechat_get_hot_search_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. Changed5 schema fields changed
    • addedOutput schema / properties / items / items / properties / keyword / title
      Added value: +"Keyword"
    • addedOutput schema / properties / items / items / properties / rank / title
      Added value: +"Rank"
    • addedOutput schema / properties / items / items / title
      Added value: +"WechatHotSearchItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / title
      Added value: +"WechatHotSearchResult"
  4. 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"
      -]New value: +[
      +  "items",
      +  "points"
      +]
  5. First observed

TDQS

A3.7/5.0
Behavior4/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. The description adds a real behavioral trait beyond them: results are not paginated, so the agent should not attempt page/cursor parameters or expect incremental fetching. It stops short of stating the result size, ordering basis of the ranking, or refresh cadence.

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, purpose first and constraint second, with no redundant restatement of the tool name. Every clause carries information an agent would otherwise have to guess.

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 tool with an output schema and readOnly/openWorld annotations, the description covers what it does and the one call-shaping constraint (no paging). Remaining gaps are minor: how many entries come back, whether the list is region/time scoped, and whether any auth/quota applies.

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; the schema is empty and fully consistent with the description. The 'no pagination' note usefully confirms that no page/cursor argument exists or should be invented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb plus resource: retrieve the WeChat Channels (视频号) hot-search/hot-ranking list. No sibling tool in the list does the same thing (the others are per-entity detail/comment/search lookups), so an agent can route to it unambiguously, though the description never explicitly contrasts itself with siblings such as 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 Guidelines2/5

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

There is no when-to-use guidance: nothing says whether this is a trending-discovery entry point versus a fallback when wechat_search_videos returns nothing. The only guidance offered is a negative constraint (no pagination), which is helpful but is not usage routing.

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