Skip to main content
Glama
soqq-wechat-search

soqq-wechat-search

by wadeld2026

微信公众号文章搜索

soqq_wechat_search

Search WeChat official account articles through Tencent's index and return real article links, account names, relative publish times, and snippets without requiring WeChat login.

Instructions

通过腾讯搜索(so.qq.com, 元宝索引)检索微信公众号文章。返回标题、真实 mp.weixin.qq.com 链接、公众号名称、相对发布时间和摘要。无需微信登录。每次约 25 条 × scrolls 轮滚动加载。适合枚举某个公众号的历史文章、追踪话题相关文章。

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": {
      "query": "<query>"
    },
    "name": "soqq_wechat_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes检索关键词,如 "Motubrain 开源" 或 "生数科技 训练报告"
scrollsNo额外滚动加载次数,每轮约多拿 25 条,默认 2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it discloses that no WeChat login is required, that results come back as real mp.weixin.qq.com links rather than redirects, and that roughly 25 items arrive per scroll round. Gaps remain around ordering, deduplication, rate limits, and what happens on empty or failed results.

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?

Four compact sentences, front-loaded with the source and action, then returns, then constraints, then use cases. Every sentence contributes information, and no phrasing is redundant.

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 two-parameter, annotation-free, no-output-schema tool, the description covers return fields, auth requirements, and result volume, which is most of what an agent needs. The one loose end is how to constrain a query to a specific public account, given the enumeration use case it advertises.

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 coverage is 100%, so both parameters are already documented in the schema, including the default of 2 scrolls and the 25-per-round yield. The description repeats the 25-per-scroll behavior but adds no new syntax for the query or guidance on how to target a single account. Baseline 3 is appropriate.

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 states a specific verb-resource pair: it retrieves WeChat public-account articles via Tencent Search (so.qq.com, Yuanbao index). Naming the underlying search source and the exact resource disambiguates it from a generic web search. It also enumerates the return fields, which pins down the tool's scope.

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?

The final sentence gives concrete use cases: enumerating a public account's historical articles and tracking topic-related articles. No alternative tools are named and no when-not-to-use conditions are stated, but with no siblings there is nothing to route against. This is clear positive guidance without exclusions.

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