Skip to main content
Glama
Sign In
WeChat Publisher MCP Server

WeChat Publisher MCP Server

by VikingMew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

wechat_list_articles

Retrieve a paginated list of published WeChat Official Account articles and optionally include each article’s HTML content for review or reuse.

Instructions

分页读取本公众号已成功发布的文章列表，可选返回正文 HTML

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wechat_list_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo每页发布记录数，1–20
offsetNo发布记录偏移量，从 0 开始
includeContentNo是否返回正文 HTML

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 load. It discloses the read-only nature, pagination, and the optional heavy HTML payload (a real performance consideration), but says nothing about limits, permissions, ordering, or what the result entries look like.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; scope, pagination, and the optional payload are all stated compactly.

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?

No output schema exists, so the description should at least sketch the shape of returned article records and the ordering of the list, which it does not. It covers the call itself but not what the agent gets back.

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 schema already defines count, offset, and includeContent fully. The description only echoes pagination and the content toggle at a high level; baseline 3 applies.

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 states a specific verb and resource ('分页读取本公众号已成功发布的文章列表') and adds a scope qualifier (successfully published). This is clearly distinct from the write siblings (create_draft, upload_cover) and from wechat_get_article_stats, though it doesn't name the differentiating sibling.

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 read-only list retrieval and mentions an optional content expansion, but gives no explicit when-to-use/when-not guidance or reasons to prefer wechat_get_article_stats for stats. Usage is inferable rather than stated.

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

Deploy Server

Other Tools