Skip to main content
Glama
redfox-data

redfox-mcp

Official
by redfox-data

wechat_search_articles

Search WeChat public account articles by keyword to access high-quality content. Return paginated results with customizable offset.

Instructions

搜索公众号文章(优质库)。keyword 必填;offset 从 0 开始、每页 +20。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNo
keywordYes
sort_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations provided, the description carries the full burden. It reveals pagination behavior ('offset 从 0 开始、每页 +20') which is helpful. However, it doesn't disclose what '优质库' means, whether results are rate-limited, or if authentication is needed. The output schema exists but is not referenced.

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?

Two concise sentences with front-loaded purpose. Every word earns its place. The pagination rule is efficiently communicated in a parenthetical. No wasted text.

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?

Given the tool has 3 params, an output schema, and no annotations, the description is minimally adequate but leaves gaps. The 'sort_type' parameter and the meaning of '优质库' are unexplained. However, with an output schema present, return values don't need documentation.

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 0%, so the description must compensate. It adds meaning for 'keyword' (required) and 'offset' (start 0, increment 20) which is not in the schema. However, 'sort_type' is not explained at all, and the description is minimal. Baseline 3 is appropriate given the partial coverage.

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?

The description clearly states it searches WeChat public account articles ('搜索公众号文章'), and adds '(优质库)' to hint at a quality filter, which differentiates it from siblings like 'wechat_search_ai_articles' and 'wechat_search_articles' (presumably a broader search). The verb 'search' and resource 'articles' are specific, though the '优质库' note is ambiguous.

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?

It provides basic use context (keyword required, offset behavior) but no explicit when-to-use or when-not-to-use guidance. Sibling tools like 'wechat_search_ai_articles' exist but are not mentioned as alternatives. The guidance is implied through the '优质库' qualifier but not explicit.

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/redfox-data/redfox-mcp'

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