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

mcp-web-print-pdf

by weixiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

printPdfByUrl

Downloads a PDF from a URL and prints it to a local printer; use preview mode to check output before printing.

Instructions

下载一个 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": {
      "url": "<url>"
    },
    "name": "printPdfByUrl"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPDF 的 http(s) 地址
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

B3.2/5.0
Behavior3/5

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

With no annotations, the description usefully discloses the critical side effect: it prints physical paper by default, while dry_run true only previews. It does not explain preview return behavior, printer defaults, permissions, error conditions, or other operational traits, but the core disruptive action is at least explicit.

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?

The description is two short clauses, front-loads the main action, and contains no filler. It is arguably too terse for such a complex tool, but every sentence earns its place.

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?

The parameter schema is very rich and covers all 8 parameters, including nested objects, so an agent can invoke the tool mechanically. However, for a complex printing tool with no annotations or output schema, the description leaves return behavior and broader operational context largely implicit.

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 documents url, dry_run, and the many nested pdf_options, print_options, and extra_options fields. The description only reiterates dry_run semantics and adds no extra meaning beyond the schema.

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: download a PDF URL and print it. It is clear enough to distinguish from printPdfByBase64 by the URL input, though it does not explicitly call out that sibling or other print alternatives.

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 only usage guidance is that default behavior prints and dry_run previews. There is no guidance on when to choose this over printPdfByBase64, printFile, or batchPrint, nor any prerequisites or exclusions.

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