pdfzen

render_template_to_pdf

Prepare a paid PDF render from one of the 45 starter templates. Validates your template + data and returns the exact, ready-to-execute HTTP request to run against pdfzen's render endpoint — POST /v402/render/pdf (x402, $0.006 USDC on Base, no API key) or POST /v1/render/pdf (pdfzen API key, credit-billed). pdfzen renders are executed over HTTP, not streamed in-band over MCP; this tool is the bridge. Your data is merged ON TOP of the starter sampleData at render time, so partial payloads inherit demo defaults (e.g. ship just the customer name + total).

Input Schema

TableJSON Schema

Name	Required	Description
`data`	No	Handlebars context. Each starter expects a specific shape — call get_starter to see the sampleData and dataKeys for the chosen slug. Your fields merge ON TOP of sampleData, so you can supply only the fields the user gave you and the rest fall back to the demo content.
`template`	Yes	Slug of the starter to render (e.g. "invoice", "receipt", "certificate"). Call list_starters first if unsure which fits the user request.
`pageOptions`	No	Page format/margin/orientation overrides. Defaults come from the starter (most are A4 portrait). Example: { "format": "Letter", "landscape": true }.

Schema Changelog

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

First observedMay 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the paid nature ($0.006 USDC), two HTTP endpoint variants, the fact that renders are executed out-of-band, and the merge-on-top behavior with sampleData. This is rich, actionable behavioral detail that goes well beyond what annotations provide.

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?

The description is dense yet efficient—each sentence adds substantive value, covering purpose, pricing, the HTTP bridge, and merge semantics. It is front-loaded with the core purpose and avoids any filler or repetition.

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 without an output schema, the description fully explains what the tool returns (an exact HTTP request), how it's executed, and the pricing model. It also references sibling tools for template discovery, making the tool completely usable in context.

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?

Input schema descriptions already cover all 3 parameters at 100%, so the baseline is 3. The description adds meaningful context by explaining that `data` merges on top of sampleData and that partial payloads inherit demo defaults, which is not present in the schema. This extra semantic value justifies a 4.

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 'Prepares a paid PDF render from one of the 45 starter templates' and explains it returns a ready-to-execute HTTP request. This specific verb and resource scope distinguish it from sibling tools like render_html_to_pdf, which handles arbitrary HTML, and get_starter/list_starters, which are informational.

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 gives clear usage context: it is a bridge for executing PDF renders over HTTP, and parameter descriptions advise calling list_starters or get_starter when unsure. However, it does not explicitly name the alternative render_html_to_pdf for non-template rendering, so it falls just short of providing explicit when/when-not guidance.

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

All pdfzen tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool serves a distinct purpose: list_starters discovers templates, get_starter retrieves template details, render_template_to_pdf renders from a starter, and render_html_to_pdf renders custom HTML. The boundary between the two render tools is clearly defined by whether a starter is used or not.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: list_, get_, render_ with clear object names (starters, starter, html, template). The naming is uniform and predictable across the set.

Tool Count5/5

With only 4 tools, the server is tightly scoped to its core workflow: discovering templates, inspecting them, and rendering PDFs. Each tool is necessary and none feel redundant or extraneous.

Completeness5/5

The tool surface covers the full lifecycle: discovery (list), investigation (get), and rendering (two variants for starter vs custom HTML). The workflow from list to get to render is fully supported, and the HTML path covers custom cases. No obvious gaps for the stated purpose.

Resources

Need Help?