Skip to main content
Glama
iTraceur

wechat-mp-search

by iTraceur

weixin_search

Search WeChat official account articles via Sogou WeChat search. Retrieve single-page results with pagination support for targeted queries.

Instructions

在搜狗微信搜索(weixin.sogou.com)中搜索微信公众号文章,返回单页结果。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo搜索结果页码,从 1 开始,默认 1
queryYes搜索关键词
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool searches Sogou WeChat and returns one page, which is a useful behavioral trait. However, it omits operational details such as possible anti-bot/captcha behavior, per-page result count, and whether the return value is raw HTML or parsed 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?

The description is one compact sentence that leads with the action and platform, then states the single-page return behavior. It contains no filler and does not duplicate schema content.

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

Completeness3/5

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

With only two well-documented parameters and no nested objects, invocation is simple. However, there is no output schema and the description only says '返回单页结果', leaving the return format and contents unspecified, which is a notable gap for downstream planning, especially with the sibling get_weixin_article_content.

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?

The schema describes both parameters with 100% coverage: 'query' is '搜索关键词' and 'page' is 1-based with a default of 1. The description adds no parameter-specific detail, but the schema already carries that burden, 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 contains a specific action ('搜索'), a target ('微信公众号文章'), and a named platform ('搜狗微信搜索/weixin.sogou.com'). The phrase '返回单页结果' distinguishes this tool from the sibling weixin_search_all, so an agent can identify 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 Guidelines4/5

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

The description's '返回单页结果' gives clear contextual scope: this tool is for retrieving a single page of search results. It does not explicitly say to use weixin_search_all for all pages, so it lacks an explicit alternative, but the context is clear enough for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iTraceur/dsh-wechat-mp-search'

If you have feedback or need assistance with the MCP directory API, please join our Discord server