wechat-article-fetcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_wechat_articleA | Fetch a public WeChat Official Account article (mp.weixin.qq.com/s/...) and return title, account_nickname, author, publish_time (+08:00), content_markdown, images and extraction_method. format: markdown | text | both. max_chars: truncate content (0 = no limit). On failure returns ok=false with error and reason; never bypass verification pages. |
| parse_wechat_htmlC | Parse a saved WeChat article page (HTML you already have) without network access. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are largely distinct: fetch_wechat_article retrieves content over the network while parse_wechat_html works on HTML the caller already has. There is minor overlap since both ultimately yield parsed article content, but the descriptions clearly signal the network/no-network boundary.
Both names follow a clean verb_noun snake_case pattern (fetch_wechat_article, parse_wechat_html) with a shared domain prefix. No mixing of conventions.
Two tools is thin, but for a narrowly scoped fetcher/parser utility each tool earns its place with a distinct mode of operation. It is appropriately minimal rather than padded.
The pair covers the core lifecycle: online fetch with formatting/truncation options and offline parsing of saved pages. Only minor gaps exist, such as no batch/multi-URL fetching or image-specific retrieval.