Skip to main content
Glama
Sign In
wechat-mcp

wechat-mcp

by RungePei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wechat_get_moments

Retrieve recent WeChat Moments posts by timeframe, with optional result limits and publisher names, so assistants can read social updates from a Windows WeChat client.

Instructions

获取最近的朋友圈内容。

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_moments"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberNo最多获取多少条，默认不限
recentNoToday | Yesterday | Week | MonthToday
with_nameNo是否同时获取发布者昵称（较慢）

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It implies a read operation but discloses nothing about auth requirements, rate limits, failure modes, or whether the fetch is paginated. Notably, it omits the 'recent' default scoping that the schema uses, leaving behavior under-specified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no waste, but it is arguably under-specified rather than genuinely concise. Minimal front-loading is present since there is only one sentence.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the schema handles all three optional parameters well. However, the description omits usage context and behavioral notes that would round out a read tool with no annotations.

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 three parameters (number, recent, with_name) are already documented in the schema, including the default value and '较慢' performance note for with_name. The description adds no parameter-level detail beyond the baseline.

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+resource combination (获取/朋友圈), making it immediately distinguishable from wechat_post_moments. However, it doesn't explicitly name siblings or clarify how it differs from related reads like wechat_get_chat_history.

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 guidance on when to use this tool versus alternatives such as wechat_get_recent_sessions or wechat_get_chat_history. No prerequisites (e.g., login state) or exclusions are mentioned.

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

Deploy Server

Other Tools