wxread MCP Server

Overview Schema Source Related Servers Discussions Admin

read_wechat_articles

Read multiple WeChat articles in sequence and convert each into clean Markdown with title, account, author, and publish-time metadata for AI processing.

Instructions

Read several WeChat articles (sequentially, with a short pause between requests).

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": {
      "urls": "<urls>"
    },
    "name": "read_wechat_articles"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes
`max_chars`	No
`include_images`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses sequential fetching with a pause between requests, but says nothing about auth requirements, failure handling when one URL in the batch fails, whether partial results are returned, or how long a multi-article call may take.

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?

A single front-loaded sentence with no wasted wording, and the sequencing caveat is placed where it matters. Its brevity is efficient rather than padded, though it borders on under-specified.

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

Completeness2/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 described, but for a 3-parameter batch tool with zero schema documentation the description leaves too much unknown: no parameter meaning, no per-URL failure semantics, no batch size expectations. Only the pacing behavior is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description explains none of the three parameters. max_chars and include_images are completely undocumented in both places, and only the plural "articles" faintly implies that urls is a list — far below what a 0%-coverage schema requires.

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?

"Read several WeChat articles" gives a specific verb and resource, and the word "several" implicitly distinguishes it from the singular sibling read_wechat_article. It stops short of explicitly naming the sibling, so an agent must infer the batch-vs-single split.

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

Usage Guidelines3/5

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

Batch usage is implied by "several" and the parenthetical sequencing note hints at the cost of multi-URL calls, but there is no explicit guidance on when to pick this over read_wechat_article, nor any limit on how many URLs are sensible.

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

Deploy Server