Skip to main content
Glama
Sign In
wechat-mcp

wechat-mcp

by jimingyuan7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Receive WeChat messages

wechat_receive

Long-poll for new inbound WeChat messages, returning only new ones per account. Automatically downloads and decrypts attached media.

Instructions

Poll for new inbound WeChat messages (one long-poll cycle). Returns messages received since the last poll; the server tracks a per-account sync cursor so repeated calls do not return duplicates. Media (images/voice/files/video) is downloaded and decrypted to local temp files by default, with the path returned in MediaPath. If multiple accounts are logged in, pass accountId.

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

Input Schema

NameRequiredDescriptionDefault
accountIdNoAccount id to poll; required only when multiple accounts are logged in.
timeoutMsNoLong-poll timeout in ms (default 35000). The server holds the request open up to this long waiting for new messages.
downloadMediaNoDownload + decrypt inbound media to temp files (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses key behaviors: long-poll mechanism, deduplication via sync cursor, default media download/decrypt to temp files, and the accountId condition. No contradictions with annotations (none exist).

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?

Three concise sentences front-load the core action, each sentence adds distinct value: purpose, behavior details, and account condition. No redundancy or fluff.

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?

While the description covers key behavioral aspects, the absence of an output schema means the description should elaborate on response structure beyond MediaPath. It mentions the sync cursor and dedup but omits other return fields like message content, sender, etc., leaving some incompleteness.

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?

Schema coverage is 100%, but the description adds context beyond schema: ties accountId to multi-account scenario, explains timeoutMs as long-poll holding time, and clarifies downloadMedia default. However, the schema descriptions are already informative, so the added value is moderate.

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 description starts with 'Poll for new inbound WeChat messages (one long-poll cycle)', which clearly states the verb (poll) and resource (inbound WeChat messages). It differs from siblings like wechat_send and wechat_listen, establishing a unique purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides context: it's a long-poll, deduplicates via sync cursor, and requires accountId only with multiple accounts. However, it does not explicitly state when not to use this tool or contrast with wechat_listen, missing explicit alternatives.

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