wechat-reader

Overview Schema Source Related Servers Discussions Admin

read_wechat_article

Read public WeChat articles and return text with metadata, pagination, and image links; falls back to a visible Chrome window when verification requires manual captcha completion.

Instructions

Read a public https://mp.weixin.qq.com/s/... article, returning text and metadata.

Omit use_browser (or use null) to try HTTP and automatically open dedicated visible Chrome on a verification page. True uses Chrome directly; False disables the browser. Any remaining captcha requires the user to verify manually. wait_seconds is 0–30. Continue a long article by passing next_offset as offset. Images are returned as links, with no OCR.

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": {
      "url": "<url>"
    },
    "name": "read_wechat_article"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`offset`	No
`max_chars`	No
`use_browser`	No
`wait_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 2, 2026

TDQS

A4.2/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does well: it discloses the HTTP-first strategy, automatic launch of visible Chrome on a verification page, the manual captcha requirement, the 0–30s wait bound, and that images are returned only as links with no OCR.

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

Conciseness4/5

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

The first sentence states purpose and return type, then operational details follow logically. It is compact and every sentence adds value, though the line-broken run-on style slightly hurts scanability.

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?

An output schema exists so return shape need not be explained. The description is complete enough for an agent to call this correctly, with only max_chars left undocumented, which is a minor omission rather than a blocker.

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 0%, so the description must compensate, and it explains use_browser's three-way semantics, wait_seconds' range, offset's role in pagination, and the URL format. It omits max_chars entirely, which is the one meaningful gap.

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?

The description gives a specific verb and resource: read a public mp.weixin.qq.com article and return text plus metadata. It is unambiguous, though there are no sibling tools to differentiate from, so it lands just below the top tier.

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?

It clearly explains how to control browser behavior: omit use_browser to try HTTP and fall back to visible Chrome, true forces Chrome, false disables it, and captcha still needs manual user verification. It also tells the agent how to continue long articles via next_offset. No alternative tools are named, but none exist.

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

read_wechat_articleA