Skip to main content
Glama
if530770

redfox-mcp-server

by if530770

wechat-rewrite

Rewrites any provided copy into engaging WeChat public account articles designed to boost readership. Uses platform-specific vocabulary and persuasive language to transform ordinary text into high-traffic content.

Instructions

一位公众号爆款文案撰写专家。具有硬核的公众号文案功底,不管给你什么文案,你总能把该文案转化为一篇高阅读数的公众号文案,文案中必定会包含一些具有公众号特色的词汇。这个角色需要具备精通语言的能力,这个角色的任务是通过语言的艺术表达,使句子更加生动、吸引人、有趣和具有说服力。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. First observedv1.0.4

TDQS

B3.3/5.0
Behavior3/5

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It states that the tool will inject WeChat-featured vocabulary and make sentences more vivid, attractive, interesting, and persuasive. However, it stays at a persona level and omits operational details like input handling, output format, or limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a flowery persona paragraph with noticeable redundancy: '具有硬核的公众号文案功底' and '需要具备精通语言的能力' overlap, and the same role/task framing is repeated. It front-loads the core idea but spends too many words restating it.

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 no-parameter generative tool, the description conveys the essential behavior and output style. However, it does not clarify how the source copy is provided or what the tool returns, which creates mild ambiguity given the empty schema and absence of an output schema.

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

Parameters4/5

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

The input schema has zero parameters, so there is nothing for the description to add beyond the empty schema. Per the baseline for 0-parameter tools, this deserves a 4; there is no ambiguity or unmet need.

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 a specific action: transforming existing copy into high-readership WeChat official account copy with platform-specific stylistic traits. It implicitly distinguishes itself from siblings like wechat-write (new copy) and xiaohongshu-rewrite (different platform), though it does not name them explicitly.

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 description implies the tool is for rewriting copy into WeChat viral style, but it provides no explicit when-to-use or when-not-to-use guidance, nor does it route to alternatives such as wechat-write or platform-specific rewriters. Usage is inferable but not directly stated.

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