Skip to main content
Glama

导出公众号 HTML

xiumi_get_html

Exports the current Xiumi article as paste-ready HTML with inline styles for WeChat, optionally saving it to a file and returning only the path and length to save context.

Instructions

通过秀米「导出 → 继续用复制粘贴」把当前文章导出为公众号可用的最终 HTML(内联样式)。设置 saveToFile 时写入文件并只返回路径和长度,避免长文占用上下文。

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": "xiumi_get_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveToFileNo保存到的绝对路径(.html);不填则直接返回 HTML 文本

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 behavioral burden. It does disclose useful behavior: the export goes through the Xiumi UI flow, and the return value differs by branch, path plus length when saving versus full HTML text otherwise. It omits preconditions, such as requiring an open article or a logged-in session, and failure modes, so an agent cannot tell what happens if the export flow is unavailable.

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?

Two compact sentences with the core action and mechanism first, followed by the conditional return behavior. Every clause carries information; the parenthetical about inline styles and the context-saving rationale are both load-bearing. Minor density in the quoted UI path, but no filler.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the definition covers the action, the mechanism, and both return branches, which is most of what an agent needs. The remaining gaps, prerequisites such as an open article or authenticated session, and behavior on failure, are modest but real for a browser-driven export.

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 coverage is 100% for the single optional parameter, so the schema already documents the absolute .html path requirement. The description adds genuinely new meaning, namely that setting it changes what is returned, path and length only instead of the HTML body. This meaning goes beyond the schema and the 3 baseline holds.

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: export the current article as final HTML usable for WeChat public accounts, with inline styles. It also states the mechanism used, Xiumi's Export → copy-paste flow, which tells an agent how this differs from generic save or screenshot tools. It stops short of explicitly naming a sibling to contrast against, but the exported-artifact scope is unambiguous.

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 only conditional guidance concerns saveToFile: set it to write to disk and avoid long HTML bloating context, leave it empty to get the text directly. That is real when-to-use guidance for the parameter but not for the tool as a whole. Nothing says when to prefer this over xiumi_save or xiumi_screenshot, and no prerequisites, such as the article being open in the editor, are stated.

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