Skip to main content
Glama
Sign In
WeChat Publisher MCP Server

WeChat Publisher MCP Server

by VikingMew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

wechat_create_draft

Save prepared HTML content to a WeChat Official Account draft and return its mediaId for later publishing. Use it to stage articles with title, author, digest, and cover image options.

Instructions

将 HTML 正文保存到公众号草稿箱，返回草稿 mediaId

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "wechat_create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes草稿标题
authorNo作者
digestNo摘要；省略时由微信处理
contentYes已准备好的 HTML 正文，原样提交，不转换 Markdown
thumbMediaIdNo已有的永久封面素材 ID；与 coverImagePath 二选一
coverImagePathNoWECHAT_COVER_DIR 内图片路径；与 thumbMediaId 二选一
contentSourceUrlNo阅读原文链接

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does add two useful facts: the operation writes to the draft box (not publishing live) and it returns a mediaId despite there being no output schema. It says nothing about authentication requirements, rate limits, draft count limits, or what happens on invalid HTML.

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 short sentence with the action and the return value front-loaded. There is no filler, and nothing about it is padded or buried.

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?

It covers the core action and return value, but for a 7-parameter write tool with no annotations and no output schema, it omits notable details: whether a cover image is effectively required (thumbMediaId/coverImagePath are mutually exclusive but not in the required list), and what the mediaId is used for downstream.

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 all seven parameters are already documented in the schema. The description's only added signal is that 'content' is pre-prepared HTML submitted as-is, which duplicates the schema's own wording. 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 names a specific verb and resource (将 HTML 正文保存到公众号草稿箱) and states the outcome (返回草稿 mediaId), so the operation is unambiguous. It does not explicitly contrast itself with siblings such as wechat_list_articles or wechat_upload_cover, but the resource ('draft') makes the distinction clear in practice.

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 or when-not-to-use guidance, and names no alternatives. It does not explain the relationship to wechat_upload_cover or the choice between thumbMediaId and coverImagePath, which matters for correct invocation.

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