SiteCheck Web Intel

WeChat Official Account articles matching a query

search_wechat_articles

Read-only

WeChat Official Account (公众号) articles matching a query, from Sogou WeChat search (weixin.sogou.com): title, summary, account name, publish time and link, 10 per page. Links are Sogou redirect links that open the mp.weixin.qq.com article in a browser. Sogou may show a captcha under heavy use; that returns 503. Related tools on this server, for a different need: search_wordpress_articles when you need WordPress.org news posts from the official WordPress news. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "search_wechat_articles"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words, Chinese or English (1 to 80 characters)
`page`	No	Result page 1 to 10 (default 1), 10 articles per page

Output Schema

Name	Required	Description	Default
`q`	No
`page`	No
`count`	No
`source`	No
`articles`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses the pagination cap (10 per page), the redirect-link behavior (Sogou links that resolve to mp.weixin.qq.com in a browser), the failure mode (captcha under heavy use returns 503), and the billing model ($0.002 USDC per successful call via x402, failures not charged). That is exactly the operational context annotations cannot convey.

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 core purpose and scope are front-loaded in the first sentence, followed by return shape, link behavior, failure note, and pricing. It is a dense block rather than separated sentences, and the pricing/related-tool clauses are slightly tacked on, but no sentence is filler.

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?

With an output schema present, the description need not explain return structure, and it still names the key fields. For a two-parameter read-only search tool it covers source, pagination, result behavior, error conditions, and cost, leaving nothing an agent needs in order to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so both q and page are already documented in the schema, and the description largely restates the 10-per-page pagination. The description does not add syntax or language nuance beyond what the schema states ('Chinese or English, 1 to 80 characters'), so the baseline of 3 applies.

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?

The description names a specific verb and resource (WeChat Official Account articles matching a query) and identifies the upstream source (Sogou WeChat search at weixin.sogou.com). It also enumerates the returned fields (title, summary, account name, publish time, link), so an agent can distinguish it from generic news search siblings like search_google_news 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 Guidelines4/5

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

It explicitly routes one adjacent need elsewhere: 'search_wordpress_articles when you need WordPress.org news posts.' That is a concrete when-to-use-this-instead signal, but it only covers one of dozens of article-search siblings, and it never states when NOT to use this tool (e.g. non-WeChat Chinese content).

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

All SiteCheck Web Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?