Skip to main content
Glama

pdf_convert_html

Convert HTML files to styled PDFs using CSS presets, page size, orientation, and custom CSS rules for controlled document output.

Instructions

Convert HTML to styled PDF

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "pdf_convert_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to input file
outputYesPath to output PDF file
presetNoCSS preset (github, elegant, minimal, branded, compact)
page_sizeNoPage size format (e.g. A4, Letter)
custom_cssNoCustom CSS rules to apply
orientationNoPage orientation (portrait or landscape)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole behavioral burden, yet it says nothing about overwriting an existing output file, whether the input path must exist locally, what happens on invalid HTML or CSS, or how presets and custom_css interact. The only behavioral hint is the word "styled", which implies CSS application but is not elaborated.

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?

A single front-loaded sentence with no filler, which is efficient. Its brevity borders on under-specification rather than being genuinely concise, but nothing in it is wasted.

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

Completeness2/5

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

For a six-parameter file-writing tool with no annotations and no output schema, the description omits key operational context: whether output paths are overwritten, whether presets are overridden by custom_css, and what the tool returns. That leaves the agent underspecified on a mutation operation.

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 format details for input, output, preset, page_size, custom_css and orientation are already documented structurally. The description adds nothing beyond a general mention of styling, which is the established baseline when the schema does the heavy lifting.

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 gives a specific verb and resource ("Convert HTML to styled PDF"), so the agent knows the transformation involved. However, it does not distinguish this tool from the very similar sibling html_to_pdf, leaving the agent to guess which one to call.

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?

There is no guidance on when to use this tool versus html_to_pdf or the other pdf_convert_* tools, and no prerequisites or exclusions are stated. The agent must infer the choice purely from the name.

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