Skip to main content
Glama
Sign In
wxread MCP Server

wxread MCP Server

by Rudy-114
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_wechat_article

Fetches a WeChat Official Account article from an mp.weixin.qq.com link and converts it into clean Markdown, with optional images, metadata, character limits, or structured JSON output.

Instructions

Read a WeChat Official Account (微信公众号) article and return it as Markdown.

Args: url: An mp.weixin.qq.com article link (short /s/xxx or long __biz=... form). include_images: Keep image links (mmbiz.qpic.cn) in the Markdown. max_chars: Truncate the body to this many characters (None = full article). as_json: Return structured JSON (title, account, author, publish_time, markdown, images...).

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

NameRequiredDescriptionDefault
urlYes
as_jsonNo
max_charsNo
include_imagesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose output shape (Markdown vs. structured JSON), truncation behavior, and image-link handling. It says nothing about network fetch requirements, WeChat cookie/auth constraints, rate limiting, or how failures (deleted/blocked articles) surface, which matters for a web-scraping tool.

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 one-line purpose is front-loaded and the args block is a compact per-parameter glossary with no filler. The unrendered docstring formatting ('Args:') is cosmetic noise but does not obscure meaning.

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?

For a four-parameter fetch tool with an output schema, the coverage is close to sufficient: it explains inputs, output mode, and truncation, and the output schema handles return structure. The only material missing piece is the relationship to read_wechat_articles and any error behavior.

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 has to explain all four parameters, and it largely does: accepted URL forms (short /s/xxx or long __biz=...), max_chars with None meaning full article, include_images tied to mmbiz.qpic.cn links, and as_json enumerating returned fields. Minor omission: it does not restate that include_images defaults to true.

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 and resource ('Read a WeChat Official Account article') plus the output format (Markdown), which is concrete and unambiguous. However, it never mentions the sibling read_wechat_articles, so an agent cannot tell from this text alone which of the two to pick.

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?

Usage is only implied by the tool name and the single-article framing; there is no explicit when-to-use or when-not-to-use statement. The existence of a plural sibling (read_wechat_articles) makes the missing differentiation a real gap rather than a formality.

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