Zovo Photo to PDF

Images to PDF

images_to_pdf

Read-onlyIdempotent

Use this when the user wants to convert JPG to PDF, PNG to PDF, combine photos into one PDF, turn scanned pages or phone photos of documents into a PDF, or make a PDF from pictures or screenshots. It places 1 to 60 JPG or PNG images in the given order, one per page, turns each photo upright from its EXIF orientation, and returns a PDF download that is kept for about 1 hour. Page size fit (each page matches its image), letter, a4 or legal; orientation auto, portrait or landscape; margin 0 to 25 mm; fit contain or cover. Does not read HEIC, WebP, GIF or TIFF (the result says how to export them), does not run OCR and does not edit pixels. Do not use for merging existing PDF files or for converting a PDF into images.

Input Schema

Name	Required	Description
`fit`	No	contain (default) shows the whole image; cover fills the page inside the margin and crops the overflow. Paper sizes only, e.g. contain.
`images`	Yes	The JPG or PNG images, in page order, e.g. scan-1.jpg, scan-2.jpg.
`margin_mm`	No	White margin on each side in millimetres, 0 to 25, e.g. 10. Default 0.
`page_size`	No	Page size, e.g. a4. fit (default) makes each page the size of its image at the image's DPI (72 when the file has none).
`orientation`	No	Paper orientation for letter, a4 or legal, e.g. auto (default: landscape for wide images, portrait otherwise). Ignored for fit.
`output_name`	No	File name for the PDF, e.g. receipts-november. Default: the first image name.

Output Schema

Name	Required	Description	Default
`file`	Yes
`note`	Yes
`pages`	Yes
`images`	Yes
`warnings`	Yes
`downloads`	Yes
`page_plan`	Yes
`pdf_bytes`	Yes
`pages_verified`	Yes
`page_plan_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds real value: EXIF auto-upright, one image per page in order, a ~1 hour download retention, and stated limits (no OCR, no pixel edits, no HEIC/WebP/GIF/TIFF). Only the exact return shape is left to the output schema, which exists.

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?

Front-loaded with the user intents first, then capabilities, then exclusions. Dense but each sentence carries distinct information; slightly long but no filler.

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?

Output schema exists so return values need no explanation; the description covers formats, ordering, limits, effects, retention, and exclusions – complete for a conversion tool of this complexity.

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 operational meaning beyond it: the 1-60 image cap, page-order semantics, and the 0-25 mm margin and fit/orientation interactions. Mostly reinforcing enum documentation already in 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?

States a specific verb+resource ('convert JPG to PDF', 'combine photos into one PDF') and enumerates distinct user intents, making it clearly distinguishable from inspect_images and from the excluded merge/PDF-to-image operations.

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?

Explicit positive triggers ('when the user wants to convert JPG to PDF...') plus explicit exclusions ('Do not use for merging existing PDF files or for converting a PDF into images') and unsupported-format guidance, so an agent knows both when and when-not to invoke it.

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

All Zovo Photo to PDF 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?