Skip to main content
Glama

pdf_to_images_batch

PDF to Images (Batch) — Apply the same rasterization configuration to up to 20 PDFs. Returns a ZIP with a subfolder per input file. [category: pdf]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dpiNoOut-of-range values clamp silently to 30-600 — never an error. Non-numeric is ignored and stays 150.
cropNoArea crop in PDF points: 'x,y,w,h'
modeNosheet/filmstrip require Starter+pages
filesYesUp to 20 input PDFs
pagesNoPage range e.g. 1-3,5,7-9. Empty = all.
formatNoAliases jpeg/tif accepted; unknown values silently stay png. avif is Starter+ — Free tier gets a 402.png
presetNoOne-click preset bundle. Explicit fields override preset values.
maxWidthNoCap width (shrink-only, preserves aspect)
sheetGapNoPixel spacing between tiles in sheet/filmstrip modes. Out-of-range clamps silently to 0-200.
colorModeNomono+jpg has no 1-bit JPEG — it silently renders grayscale and sets X-Color-Mode-Adjusted. Unknown values fall back to rgb.rgb
maxHeightNoShrink-only height cap in pixels, aspect preserved. Omit for no cap — an explicit 0 clamps UP to 100 and shrinks every page.
avifQualityNoAVIF quality (Starter+)
jpegQualityNoConsulted only when format=jpg. Out-of-range clamps silently to 50-95 — this is not a 0-100 scale.
namePatternNoFilename template with {basename}/{page}/{page:03d}/{dpi}/{format}/{date} tokens
transparentNoPNG alpha channel when true
webpQualityNoConsulted only when format=webp. Out-of-range clamps silently to 50-95 — this is not a 0-100 scale.
sheetColumnsNomode=sheet only — filmstrip is always one row. Out-of-range clamps silently to 1-10.
watermarkFontNoOutside the enum it silently becomes Helvetica. Does nothing unless watermarkText is set.Helvetica
watermarkTextNoOptional text watermark stamped on each image
watermarkTileNoACCEPTED BUT UNUSED in this tool — no tiling on rasterized pages; the stamp renders once at watermarkPosition.
watermarkColorNoHex color, #rgb or #rrggbb.#808080
watermarkScaleNoACCEPTED BUT UNUSED in this tool — the raster stamp sizes by watermarkFontSize only; set that instead.
backgroundColorNoBackground for transparent PDFs rendered to non-alpha formats#FFFFFF
sheetBackgroundNoCanvas color behind tiles, sheet/filmstrip modes only. #rgb or #rrggbb; invalid hex silently keeps #FFFFFF.#FFFFFF
tiffCompressionNoTIFF compression (format=tiff only).lzw
watermarkOpacityNo0 invisible to 1 solid; out-of-range clamps. NOT a percent — 50 renders fully opaque. Needs watermarkText.
watermarkFontSizeNoPoints against the bitmap's 72dpi density — at dpi=300 text is ~4x smaller on the page than in a PDF. Needs watermarkText.
watermarkPositionNoUnknown codes silently become c (center). Does nothing unless watermarkText is set.c
watermarkRotationNoInteger degrees only — a decimal like '45.5' silently resets to 45. Needs watermarkText.

Schema Changelog

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

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds useful behavioral context by stating the output format (ZIP) and the per-input subfolder structure, which an agent would not otherwise know without calling the tool.

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 a single focused sentence that front-loads the tool's purpose, states the batch limit, and names the output shape. The trailing '[category: pdf]' is a minor structured tag, not padding, and there is no wasted wording.

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?

For a tool with 29 parameters and no output schema, the description provides the critical selection information (batch size limit, uniform configuration, ZIP output layout) while leaving parameter-level details to the thoroughly documented schema. It is slightly light on failure/tier behavior, but the schema already warns about tier-gated features, so this is adequate.

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 every parameter has its own detailed description with defaults, ranges, and edge cases. The tool description adds only the high-level 'same configuration' idea, which is useful but does not substantially extend what the schema already provides, so a baseline 3 is appropriate.

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 names a specific verb ('Apply'), a clear resource ('rasterization configuration to up to 20 PDFs'), and a concrete deliverable ('Returns a ZIP with a subfolder per input file'). This distinguishes it from the sibling pdf_to_images by emphasizing batch processing and ZIP packaging.

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 makes the batch context explicit with 'same rasterization configuration to up to 20 PDFs', which clearly implies this tool is for processing multiple PDFs at once. It does not explicitly name pdf_to_images as the single-file alternative, so it stops short of a full when-to-use/when-not-to-use statement.

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

Try in Browser

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