Skip to main content
Glama
if530770

redfox-mcp-server

by if530770

wechat-10w-hot

Find WeChat articles exceeding 100,000 reads by selecting a category and date range. Get trending popular content for targeted periods to support content research and planning.

Instructions

公众号10w+爆文查询,按分类和时间获取10w+阅读热门文章

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo分类:总排名/科技数码/健康养生 等23个标准分类总排名
endDateYes结束日期 YYYY-MM-DD
startDateYes起始日期 YYYY-MM-DD(支持 yesterday 等)

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 burden of behavioral disclosure. It does convey a read-only lookup of 100k+ read articles filtered by category and date, but it does not disclose result format, result limits, sorting behavior, or handling of invalid date/category values.

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 short sentence with the main action front-loaded and no filler. It is slightly redundant in that '公众号10w+爆文查询' and '获取10w+阅读热门文章' restate the same core idea, but this is minor.

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 3-parameter query tool, the core inputs and selection criteria are documented. However, with no output schema and no annotations, the description still leaves the agent without a clear picture of the return payload or any usage constraints, so it is only minimally complete.

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 baseline is 3. The description only repeats the 'by category and time' idea already present in the parameter schema and adds no additional format, relationship, or default-value context.

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 names a specific action (查询/获取) and resource (公众号10w+爆文/10w+阅读热门文章) and states the key filtering scope: category and time. It is clearly distinguishable from WeChat sibling tools by the '10w+' threshold and category/time focus.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no exclusions, and no mention of alternatives. Among many related WeChat tools, the agent is left to infer when this tool should be chosen over tools like wechat-original-hot or wechat-search.

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