Skip to main content
Glama
yuanbao-search-mcp

yuanbao-search-mcp

by GtJerry111

Read a WeChat article

yuanbao_read_weixin_article
Read-only

Read a WeChat official-account article from an mp.weixin.qq.com URL and return its full text, title, account, publish time, Markdown body, character counts, truncation status, and image URLs.

Instructions

Read a WeChat official-account article and return its full text.

Args: url: An http(s) URL on mp.weixin.qq.com. max_chars: Maximum characters to return, 1,000-100,000. Defaults to the server-configured limit.

Returns: Title, account, publish time, lightweight Markdown body, character counts, truncation flag, and up to 50 content image URLs.

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": "yuanbao_read_weixin_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
max_charsNo

Output Schema

NameRequiredDescriptionDefault
urlYes
titleYes
imagesNo
accountNo
contentYes
truncatedYes
char_countYes
image_countNo
publish_timeNo
original_charsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, open-world and non-idempotent, so the description properly focuses on output behavior instead of repeating safety claims. It discloses truncation via max_chars, that a truncation flag and character counts are returned, and the image-URL cap of 50 — genuinely useful behavioral context. It stops short of noting failure modes such as restricted, deleted, or login-gated articles.

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?

Front-loaded with a one-line purpose, then tightly organized Args/Returns sections with no filler. Every clause — domain constraint, range, truncation flag, image cap — conveys actionable information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description does not need to exhaustively document return values, yet it summarizes them well enough to set expectations. For a simple two-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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 description coverage is 0% and neither parameter has a description in the schema, so the description carries the full burden — and it does: the url domain restriction plus the max_chars bounds (1,000–100,000) and default behavior add real meaning. Minor tension: it says the default is the "server-configured limit" while the schema declares 20000, which an agent could find slightly ambiguous.

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?

States a specific verb and resource ("Read a WeChat official-account article and return its full text"), which cleanly separates it from the sibling search tools that find articles rather than read them. The scope is unambiguous and an agent can select it without opening the schema.

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?

The url arg constraint ("An http(s) URL on mp.weixin.qq.com") implicitly tells the agent this is for an already-known article URL, which is useful routing signal. However, it never explicitly says when to use this versus yuanbao_search_weixin_articles, nor what happens with non-mp.weixin.qq.com URLs or missing/paywalled articles.

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