Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco

html_to_pdf

Convert HTML code into PDF documents, with options for custom headers, footers, margins, and page orientation.

Instructions

Convert HTML to PDF.
Ref: https://developer.pdf.co/api/pdf-from-html/convert.md

The header and footer parameters can contain valid HTML markup with the following classes used to inject printing values into them:
- date: formatted print date
- title: document title
- url: document location
- pageNumber: current page number
- totalPages: total pages in the document
- img: tag is supported in both the header and footer parameter, provided that the src attribute is specified as a base64-encoded string.
For example, the following markup will generate Page N of NN page numbering:
```html
<span style='font-size:10px'>Page <span class='pageNumber'></span> of <span class='totalPages'></span>.</span>

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlYesInput HTML code to be converted. To convert the link to a PDF use the /pdf/convert/from/url endpoint instead. If it is a local file, just pass the file content as a string.
nameNoFile name for the generated output. (Optional)
footerNoUser definable HTML for the footer to be applied on every page footer. (Optional)
headerNoUser definable HTML for the header to be applied on every page header. (Optional)
api_keyNoPDF.co API key. If not provided, will use X_API_KEY environment variable. (Optional)
marginsNoSet to CSS style margins like 10px, 5mm, 5in for all sides or 5px 5px 5px 5px (the order of margins is top, right, bottom, left). (Optional)
mediaTypeNoUses print by default. Set to screen to convert HTML as it appears in a browser or print to convert as it appears for printing or none to set none as mediaType for CSS styles. (Optional)
paperSizeNoA4 is set by default. Can be Letter, Legal, Tabloid, Ledger, A0, A1, A2, A3, A4, A5, A6 or a custom size. Custom size can be set in px (pixels), mm or in (inches) with width and height separated by space like this: 200 300, 200px 300px, 200mm 300mm, 20cm 30cm or 6in 8in. (Optional)
orientationNoSet to Portrait or Landscape. Portrait is set by default. (Optional)
httppasswordNoHTTP auth password if required to access source url. (Optional)
httpusernameNoHTTP auth user name if required to access source url. (Optional)
printBackgroundNotrue by default. Set to false to disable printing of background. (Optional)
DoNotWaitFullLoadNofalse by default. Set to true to skip waiting for full load (like full video load etc. that may affect the total conversion time). (Optional)
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It offers valuable detail on header/footer placeholders but omits return format, authentication requirements, async behavior, or any side effects, leaving major behavioral unknowns.

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 well-structured with a clear opening, a reference link, and a focused breakdown of header/footer capabilities. The example is concise and helpful. No unnecessary filler.

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?

As a conversion tool with no output schema and no annotations, the description lacks essential contextual information: what is returned (PDF binary/link), whether this is asynchronous, and how it differs from webpage_to_pdf for URL inputs. It covers only header/footer semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, meeting the baseline of 3. The description adds substantial extra semantics for the header and footer parameters with usable classes, img support, and a concrete example, which goes beyond schema descriptions.

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 clearly states the action (Convert HTML to PDF) and resource (HTML input). It is distinctive by name and matches the tool, but it doesn't explicitly contrast with sibling tools like webpage_to_pdf or document_to_pdf.

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 main description gives no guidance on when to use this tool versus siblings. While the schema for the html parameter hints at using a different endpoint for links, the tool description itself lacks this context or any alternatives.

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/pdfdotco/pdfco-mcp'

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