redfox-mcp

Official

Overview Schema Source Related Servers Discussions Admin

wechat_get_user_works

Fetch WeChat Official Account article lists by account ID, with options to sort by default, latest, or hottest and filter by publish date range.

Instructions

获取公众号文章列表（优质库）。account 为公众号微信号（必填）； sort_type：_0=默认，_2=最新，_4=最热；publish_time_start/end 格式如 "2026-07-01"。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>"
    },
    "name": "wechat_get_user_works"
  }
}

Input Schema

Name	Required	Description	Default
`offset`	No
`account`	Yes
`sort_type`	No
`account_name`	No
`publish_time_end`	No
`publish_time_start`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the 'account' field is required and explains sort_type and date format, but does not state whether the operation is read-only, if pagination is supported (offset is there but not explained), or if there are any rate limits or safety concerns.

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

Conciseness3/5

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

The description is short but contains useful detail. It front-loads the main purpose and explains key parameters. However, it mixes Chinese and English, and could be more structured (e.g., grouping optional params).

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 6-parameter input, no annotations, and an output schema present, the description provides enough to get started but omits details on 'offset', 'account_name', and return value expectations. It is adequate but not thorough.

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 'account', 'sort_type', and date parameters, but does not describe 'offset' or 'account_name'. With 6 parameters and only 3 explained, it partially compensates but leaves gaps.

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 '获取公众号文章列表（优质库）' which translates to 'get WeChat official account article list (quality library)' and specifies that 'account' is required. This is a specific verb+resource combo, but it does not distinguish itself from siblings like 'wechat_get_work' or 'wechat_search_articles'.

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 explains parameter choices (e.g., sort_type values, date format) but does not provide guidance on when to use this tool versus alternatives like 'wechat_search_articles' or 'wechat_get_work'. No exclusions or alternatives are mentioned.

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

Deploy Server