Skip to main content
Glama
weinh

wechat-mcp-publisher

by weinh

create_news_draft

Create a WeChat Official Account news draft by submitting HTML content, title, and cover image. Automatically uploads embedded images to WeChat and returns the media ID, title, and cover URL.

Instructions

创建图文草稿(news),成功返回 {"media_id": ..., "title": ..., "cover_url": ...}。

参数:
  title: 文章标题(必填)
  content: 正文。支持两种形态——HTML 字符串,或本地 .html 文件路径
           (若该路径存在则自动读取文件,否则按 HTML 内容处理)
  cover: 封面图片(必填):本地文件路径或 http(s) URL,自动上传为封面素材
  author: 作者名(可选)
  digest: 摘要(可选,留空时微信自动截取正文)
  content_source_url: 原文链接(可选)

正文 HTML 中的 <img> 会自动上传到微信并替换 src 为微信托管的 URL;
已指向微信域名(mmbiz.qpic.cn / mp.weixin.qq.com)的图片保持不变。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coverYes
titleYes
authorNo
digestNo
contentYes
content_source_urlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are present, so the description carries full responsibility. It discloses several non-obvious behaviors: content may be a file path that is auto-read, cover is auto-uploaded, <img> URLs are rewritten to WeChat-hosted URLs while WeChat-domain images are left intact, and an empty digest triggers automatic extraction. This is well beyond baseline.

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?

The description is front-loaded with purpose and return value, then organized as a labeled parameter list. Every sentence adds operational value, including the image-handling note, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter creation tool with an output schema, the description covers input formats, side effects, image handling, and return shape. No gaps remain for an agent to call it correctly.

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

Parameters5/5

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

Schema descriptions are 0% covered, and the description compensates fully by explaining each parameter (title, content with dual forms, cover with path/URL and auto-upload, author, digest fallback, content_source_url). It adds requiredness and behavioral nuances the schema lacks.

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 opens with a specific verb ('创建' - create) and resource ('图文草稿(news)'), and names the successful return fields. It clearly identifies the tool's function and is distinguishable from sibling tools like delete_draft or list_drafts by the create/news-specific framing.

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?

No explicit comparison to siblings is provided. The intended use case (creating a news draft) is implied by the name and the headline phrase, but the description does not state when to choose this over create_newspic_draft or when not to use it.

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/weinh/wechat_mcp_publisher'

If you have feedback or need assistance with the MCP directory API, please join our Discord server