Zovo Booklet Print

Make a print booklet from a PDF

make_booklet

Read-onlyIdempotent

Use this when the user wants to print a PDF as a booklet (saddle stitch: print double-sided, fold in half, staple), make a zine or program booklet, or put 2 or 4 pages per sheet side for a handout. Takes one attached PDF (up to 200 pages), layout booklet, 2up or 4up, sheet auto, letter, a4, tabloid or a3, binding left or right, gutter in mm and creep in mm for thick booklets, and returns the imposed PDF, the page order per sheet side, a CSV of the order and the print setting. Blank pages are added at the end to fill a booklet to a multiple of 4. Does not open password-protected or restricted PDFs, does not carry links or form fields, and does not print. Do not use to merge or split PDFs.

Input Schema

Name	Required	Description
`file`	Yes	The PDF to print as a booklet, e.g. program.pdf.
`sheet`	No	Paper to print on: auto (default: the standard size closest to the PDF's first page), letter, a4, tabloid (11 x 17 in) or a3.
`layout`	No	booklet (default: pages in fold order, 2 per sheet side, to fold and staple in the middle), 2up (2 pages per sheet side in reading order) or 4up (4 pages per sheet side).
`binding`	No	left (default, for left-to-right books) or right (right-to-left books such as Arabic or Hebrew: the first page sits on the right).
`creep_mm`	No	Booklet only: millimetres to shift the innermost sheet's pages toward the fold (outer sheets shift less), 0 to 2, e.g. 0.5 for 40 or more pages. Default 0.
`gutter_mm`	No	Extra space in millimetres between the pages on a sheet (at the fold for a booklet), 0 to 20, e.g. 6. Default 0.

Output Schema

Name	Required	Description	Default
`file`	Yes
`check`	Yes
`notes`	Yes
`pages`	Yes
`print`	Yes
`sheet`	Yes
`table`	Yes
`layout`	Yes
`sheets`	Yes
`binding`	Yes
`creep_mm`	Yes
`downloads`	Yes
`gutter_mm`	Yes
`slot_names`	Yes
`output_name`	Yes
`sheet_label`	Yes
`sheet_sides`	Yes
`table_count`	Yes
`blanks_added`	Yes
`layout_label`	Yes
`padded_pages`	Yes
`scale_percent`	Yes
`output_size_kb`	Yes
`expires_in_hours`	Yes
`sheets_single_sided`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses a 200-page input cap, that blank pages are appended to reach a multiple of 4, that password-protected/restricted PDFs are rejected, that links and form fields are dropped, and that nothing is actually printed. That is exactly the behavioral context the annotations alone cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded 'Use this when...' opening and the trailing exclusions are well placed, but the middle collapses every parameter option into one long run-on sentence that repeats the schema. The parameter recital could be cut with no loss to an agent that reads the schema.

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?

An output schema exists and the description still sketches the returns, and it covers limits, defaults, and failure modes, so an agent has enough to call it correctly. The one missing piece is the relationship to plan_booklet, which matters given this is a two-tool family.

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%, and the description largely re-enumerates the same option sets (booklet/2up/4up, auto/letter/a4/tabloid/a3, left/right), which earns little credit. It does add modest meaning by explaining creep and gutter in terms of thick booklets and the fold, but the enumerations are duplicative of structured fields.

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 names a specific verb and resource (impose a PDF as a saddle-stitch booklet) and covers the concrete outputs: imposed PDF, page order per sheet side, and CSV. It does not, however, distinguish itself from the sibling plan_booklet, so an agent cannot tell from the description alone why one exists versus the other.

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?

It gives clear trigger cases ('user wants to print a PDF as a booklet', 'make a zine or program booklet', 'put 2 or 4 pages per sheet side for a handout') and a negative boundary ('Do not use to merge or split PDFs'). The main gap is that the only sibling, plan_booklet, is never named as the alternative for planning versus rendering.

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

All Zovo Booklet Print tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?