Skip to main content
Glama

HTML to PDF

document.pdf.from_html
Read-onlyIdempotent

Generate PDF documents from HTML content using headless Chrome—renders CSS, JavaScript, custom page size, margins, and headers. Provides a temporary download link.

Instructions

Convert HTML content to a PDF document using headless Chrome — full CSS + JavaScript rendering, custom page size, margins, headers/footers, background colors. Returns a temporary download URL for the generated PDF (API2PDF)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlYesHTML content to convert to PDF (full document or fragment, e.g. "<h1>Report</h1><p>Content here</p>")
fileNameNoOutput filename (e.g. "report.pdf")
optionsNoPDF rendering options (page size, margins, header/footer)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.5.0
  2. Removedv1.0.20
  3. Addedv1.0.15
  4. Removedv1.0.14
  5. Addedv1.0.12

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already show readOnlyHint=true and idempotentHint=true. The description adds behavioral context: headless Chrome rendering, temporary download URL, and customization options. No contradiction with annotations.

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 compact sentences with no unnecessary words. Front-loaded with the core action ('Convert HTML content to a PDF document') followed by key features and output details.

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?

Given the presence of an output schema, the description adequately covers input, process, and output (temporary download URL). It explains the rendering engine and customization options, though could mention authentication or file size limits if applicable.

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 all parameters. The description mentions customizable options (page size, margins, headers/footers) which maps to the 'options' parameter but adds minimal new detail beyond the schema.

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 clearly states the tool converts HTML to PDF using headless Chrome, with full CSS/JS rendering and customization. It specifies the input (HTML content) and output (temporary download URL). This distinguishes it from siblings like 'document.pdf.from_url' which converts from a URL.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for direct HTML content, contrasting with sibling 'document.pdf.from_url'. However, it does not explicitly state when to use it versus alternatives or mention prerequisites like file size limits.

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/whiteknightonhorse/APIbase'

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