Skip to main content
Glama
if530770

redfox-mcp-server

by if530770

wechat-write

Search viral WeChat articles by keyword to get creative references for your own writing. Use to align content with proven successful formats.

Instructions

公众号爆款文章写作参考,基于关键词查询同赛道爆款文章供创作参考

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes创作方向关键词
maxItemsNo返回数量
startDateNo起始日期 YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.4

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully clarifies that despite the 'write' name, the tool is a read-oriented query/reference tool, not a publishing or rewriting tool. It does not disclose output structure, sort order, or whether full article content or just metadata is returned.

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 description is one compact, front-loaded sentence that states the purpose before the mechanism. Minor redundancy between '写作参考' and '供创作参考' exists, but it does not hurt readability.

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?

For a simple keyword-based lookup tool, the description plus fully documented schema is workable: an agent knows to pass a keyword and can infer results are viral articles for reference. However, without an output schema, it would benefit from specifying whether results include titles, links, content snippets, or engagement metrics.

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 the parameters are already documented. The description adds little beyond rephrasing 'keyword' as the creative direction, but does not need to compensate for missing schema documentation.

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 identifies the tool as a WeChat Official Account viral-article writing reference that queries same-track hit articles by keyword. This distinguishes it from general search or rewriting tools, though it does not explicitly name a sibling alternative.

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 phrase '供创作参考' implies the tool should be used during content creation to gather inspiration from viral articles. However, it gives no explicit when-to-use, when-not-to-use, or alternative tool guidance.

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

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