John's Essentials

pdf_excel_to_pdf_batch

Excel to PDF (Batch) — Apply the same Excel-to-PDF configuration to up to 20 spreadsheets. Returns a ZIP with per-file subfolders. [category: pdf]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pdfa`	No	Archival PDF/A output. 2b is the safe default.	none
`files`	Yes	Up to 20 input spreadsheets
`scale`	No	Print scaling percent. Overrides fitToPage when set.
`footer`	No	Per-page footer template. Same tokens as header.
`header`	No	Per-page header template. Tokens: {page}, {pages}, {sheet}, {date}, {filename}.
`sheets`	No	Sheet selection: 'all', comma-separated names (e.g. 'Sales,Ledger'), or comma-separated 0-based indexes (e.g. '0,2'). Non-selected sheets are hidden before conversion.
`margins`	No	default\|narrow\|normal\|wide (Excel's inch presets); default keeps the sheet's own margins. Only applies to .xlsx input; unknown → default.	default
`quality`	No	Output compression quality preset.
`password`	No	Open password for the output PDF (user password).
`bookmarks`	No	Add PDF bookmarks, one per sheet.
`fitToPage`	No	Fit each sheet to a page. 'width' prevents column cutoff; 'one-page' squeezes each sheet onto a single page.	none
`gridlines`	No	Show gridlines. Empty leaves the sheet's own setting.
`paperSize`	No	a4 (default) \| letter \| legal \| tabloid \| a3. Only applies to .xlsx input (excelize preprocess); unknown values silently become a4.	a4
`splitMode`	No	combined = one multi-page PDF; per-sheet = ZIP with one PDF per sheet.	combined
`repeatRows`	No	Print titles — rows that repeat on every page. e.g. '1' or '1-3'.
`orientation`	No	Page orientation. 'auto' picks landscape for sheets with ≥8 data columns.	auto
`showHeaders`	No	Show row/column headers (A/B/C + 1/2/3). Empty leaves the sheet's own setting.
`permPassword`	No	Owner password for permission restrictions. Optional.
`watermarkText`	No	Optional text watermark stamped on every page of the output.

Schema Changelog

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

First observedSep 5, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds genuinely useful behavior beyond the annotations: the output wrapper format (ZIP), the per-file subfolder structure, the 20-file limit, and the uniform-configuration guarantee. The annotations already cover the safety profile (non-read-only, non-destructive), and the description does not contradict them.

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 core description is a single 18-word sentence that front-loads the batch scope, the limit, and the output format, then stops. The '[category: pdf]' tag is minor metadata, but every substantive element earns its place with zero redundancy.

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?

Given no output schema, the description wisely covers the return structure (ZIP with per-file subfolders), the scale limit, and the uniform-config behavior — the batch-specific facts an agent cannot infer. With the 19-parameter semantics fully handled by the schema and the detailed single-file semantics living in pdf_excel_to_pdf, nothing essential is missing.

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%, so all 19 parameters are already documented in the schema and the description need not compensate. The phrase 'same Excel-to-PDF configuration' hints the parameters mirror the single-file tool but adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb and resource ('Apply the same Excel-to-PDF configuration to up to 20 spreadsheets') and clearly defines the output ('Returns a ZIP with per-file subfolders'). The batch scope and 20-file limit distinguish it from the sibling pdf_excel_to_pdf without needing to open the schema.

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

Usage Guidelines3/5

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

The batch context is clear ('up to 20 spreadsheets', 'same configuration'), so an agent can infer it is for multi-file jobs. However, the description never explicitly names the single-file alternative pdf_excel_to_pdf or states when NOT to use this tool, leaving the routing decision to inference from the tool name.

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

All John's Essentials 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

B3.2/5.0

Disambiguation2/5

Multiple tool pairs are near-identical: octopus_mkdir/octopus_make_folder and octopus_move/octopus_move_file are literal duplicates, analyze_hash/generate_hash both compute hashes, convert_word_to_pdf overlaps convert_document, and photo_compress/photo_compress_to_size plus pdf_thumbnails/pdf_to_images have fuzzy boundaries. The descriptions are detailed and cross-reference each other helpfully, but at 144 tools an agent will regularly misselect.

Naming Consistency3/5

The dominant {category}_{verb}_{object} snake_case pattern (pdf_*, photo_*, convert_*, analyze_*, media_*) is largely consistent and predictable. However, outliers like chatwithyourpdf and describe_image break the category-prefix convention, and the octopus namespace mixes bare verbs (read, write, mkdir) with verb_noun forms (make_folder, move_file, search_meta) inconsistently.

Tool Count2/5

144 tools is an extreme count for any MCP server. The broad scope (PDF, photo, video, audio, conversion, analysis, generation, file storage, web, e-sign) justifies some volume, but the count is inflated by batch and inspect variants (pdf_to_excel + batch + inspect), duplicate tools, and overlapping converters. An agent faces an overwhelming selection surface.

Completeness4/5

Per-domain coverage is remarkably deep: PDF spans merge/split/compress/protect/unlock/metadata/OCR/watermark and bidirectional conversion; photo covers editing, format conversion, face handling, OCR, and collage; file storage has full CRUD plus search. Minor gaps exist (no audio transcription, no video metadata editing, no deletion of PDF pages is actually covered via pdf_delete_pages) but the surface has no dead ends for its declared domains.

Resources

Need Help?