Skip to main content
Glama
Sign In
mcp-web-print-pdf

mcp-web-print-pdf

by weixiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

printHtml

Render an HTML string as a PDF and send it to a local printer, or set dry_run to true to preview without printing.

Instructions

把 HTML 字符串渲染成 PDF 并打印。默认真正出纸；dry_run: true 才只渲染预览

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": {
      "html": "<html>"
    },
    "name": "printHtml"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYes完整页面或 HTML 片段
copiesNo便捷参数：份数
dry_runNofalse（默认）= 真正出纸；true = 只渲染预览。显式 extra_options.action 优先于本项
pdf_optionsNoPDF 排版选项（字段与客户端 pdfOptions 白名单一致，未知字段会报错）
paper_formatNo便捷参数：纸张名。标准纸名会同时写入 pdf_options.paperFormat 与 print_options.paperFormat；其它纸名只写后者
printer_nameNo便捷参数：打印机名，留空用系统默认打印机
extra_optionsNo额外选项：action/requestTimeout/cookies/httpHeaders/localStorages/sessionStorages，以及任意自定义键（会原样返回）
print_optionsNo打印机选项（字段与客户端 printOptions 白名单一致，未知字段会报错）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the single most consequential trait: it physically prints paper by default, and preview requires an explicit opt-in. That is a genuine side-effect warning beyond the schema. It stops short of mentioning that output goes to the system default printer unless printer_name is set, or that unknown option fields raise errors.

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?

Two short sentences, front-loaded with the purpose and then the default-behavior warning. Nothing is padded and the key risk (real printing) lands before any optional detail.

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 complex tool (8 top-level params, deep nesting) with no annotations and no output schema, the description covers purpose and the default-vs-preview decision, which are the decisive facts. It is slightly thin on printer selection defaults and on what a successful call yields, though the schema partly covers the latter via the action=preview description.

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% and every parameter, including deeply nested pdf_options/print_options/watermark fields, is documented in the schema itself. The description only restates html and dry_run, which the schema already explains in more detail, so it adds no meaning beyond structured data. 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?

States a specific verb pair (渲染成 PDF 并打印) and the resource (HTML 字符串), which implicitly separates it from the URL/base64 siblings in the print* family. However, it never names those siblings, so the distinction rests on the agent noticing '字符串' versus 'ByUrl'/'ByBase64'.

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 line '默认真正出纸；dry_run: true 才只渲染预览' gives real guidance on print-versus-preview intent. But there is no routing guidance among the many siblings (printHtmlByUrl, printHtmlByBase64, printPdfBy*), so an agent holding a URL or base64 payload gets no explicit nudge to a different tool.

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