ReflowPDF

Print HTML to PDF

render_pdf

Lays out a whole HTML document (with its CSS) as paged print and returns a download link to the PDF, valid 24 hours, and the document's edit link in the ReflowPDF editor (give the person both). Use @page for paper and margins, margin boxes for headers, footers and page numbers; JavaScript does not run. Read read_guide topic "html" before the first document. To change the document later, use update_document with its document_id.

Input Schema

Name	Required	Description
`html`	Yes	The whole HTML document: <!doctype html>, <html lang>, a <title>, a <style> in <head> with @page. Self-contained; images and fonts by https URL, data: URI or an upload_image link.
`preview`	No	A picture (PNG) of page 1 comes with the answer, so you can check the layout, fonts and images before giving the links. Default: true.
`filename`	No	The PDF file name, e.g. "invoice-1042.pdf". Default: the document's <title>.

Output Schema

Name	Required	Description
`url`	Yes	The link, valid 24 hours.
`mark`	Yes	Whether the PDF carries the ReflowPDF mark, and why.
`bytes`	Yes
`notes`	Yes	What to tell the person about this PDF.
`pages`	Yes
`timing`	No	The engine's own parts of it, when it states them: layoutMs (styles, layout and pagination) and writeMs (writing the PDF).
`editUrl`	No	The document in the ReflowPDF editor: the person edits it there (the link is the document; it lasts while it is used).
`preview`	No	What picture of the PDF came with this answer (page 1, as PNG), or why none did.
`filename`	Yes
`renderMs`	No	How long the print took on the server, in milliseconds (the engine and its adapter).
`revision`	No	Its revision: name it to update_document as base_revision.
`expiresAt`	Yes	When the link stops working (ISO 8601).
`documentId`	No	The document, for get_document and update_document.
`missingVariables`	No	Template values the data did not have (printed empty).
`skippedResources`	No	Images, fonts or style sheets the server could not fetch.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026

addedInput schema / properties / preview

Added value: +{
+  "description": "A picture (PNG) of page 1 comes with the answer, so you can check the layout, fonts and images before giving the links. Default: true.",
+  "type": "boolean"
+}

addedOutput schema / properties / preview

Added value: +{
+  "description": "What picture of the PDF came with this answer (page 1, as PNG), or why none did.",
+  "type": "string"
+}

addedOutput schema / properties / renderMs

Added value: +{
+  "description": "How long the print took on the server, in milliseconds (the engine and its adapter).",
+  "type": "integer"
+}

addedOutput schema / properties / timing

Added value: +{
+  "description": "The engine's own parts of it, when it states them: layoutMs (styles, layout and pagination) and writeMs (writing the PDF).",
+  "properties": {
+    "layoutMs": {
+      "type": "number"
+    },
+    "writeMs": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Adds substantial context beyond annotations: the download link expires in 24 hours, JavaScript does not run, and the response contains two links that must both be surfaced. Annotations already cover the safety profile (openWorld, non-idempotent, non-destructive), and the description complements them rather than contradicting. It stops short of stating explicitly that each render creates a new persistent document, which the 'edit link' and update_document reference only imply.

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?

Front-loaded with the core action and outputs, then prerequisites and authoring hints. Every sentence carries distinct information (outputs, expiry, CSS technique, JS limitation, prerequisite reading, follow-up tool) with no redundancy.

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

Completeness5/5

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

Even though an output schema exists, the description explains the practical return values (two links, 24h expiry) and the preview/filename defaults are covered in the schema. Prerequisites, follow-up path, and CSS authoring constraints are all present, so an agent can call this correctly on the first attempt.

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%, so the baseline is 3, but the description adds real meaning about the html parameter's required shape (@page for paper and margins, margin boxes for headers/footers/page numbers, no JavaScript) and clarifies that both returned links should be given to the user. This is guidance the schema alone would not supply.

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?

States a specific verb and resource ('lays out a whole HTML document ... as paged print') plus the concrete output (a PDF download link valid 24 hours and an editor edit link). It also distinguishes itself from siblings by naming update_document for later edits and read_guide for prerequisites.

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

Usage Guidelines5/5

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

Explicitly tells the agent to read read_guide topic "html" before the first document, and to use update_document with document_id for subsequent changes rather than re-rendering. The 'give the person both' instruction and the @page/margin-box guidance define how to use it correctly.

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

All ReflowPDF tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?