convertfilefast

images_to_pdf

Idempotent

Combine multiple images into one multi-page PDF.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filenames`	No	Optional filenames matching files_base64, with extensions.
`page_size`	No	Page size: fit, A4, or letter.	fit
`output_name`	No	Name for the output PDF.	images.pdf
`source_urls`	No	Public image URLs to combine into a multi-page PDF, in order.
`files_base64`	No	Base64-encoded image files to combine, in order.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

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

First observedJun 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations provide idempotentHint and openWorldHint, indicating safe and idempotent behavior. The description adds no extra context (e.g., no mention of image resizing, file handling, or output behavior). With annotations present, a score of 3 is appropriate as the description does not contradict them but adds minimal value.

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?

Single sentence, no redundant words, front-loaded with the key action. Efficient.

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 simple tool with an output schema and annotations, the description is nearly complete. It covers the core function without missing critical aspects. One minor gap is no mention of output format or success criteria, but this is mitigated by the output schema.

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 the input schema already documents all parameters. The description does not add any parameter-level meaning beyond what is in the schema. Baseline 3 is correct.

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 'Combine multiple images into one multi-page PDF.' clearly states the function: verb (combine), resource (images), and outcome (multi-page PDF). It distinguishes from siblings like merge_pdfs (which combines PDFs) and compress_image.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for converting images to PDF, but does not mention when to prefer it over merge_pdfs or other sibling tools. Context is only implied by the tool name and description.

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

All convertfilefast 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

A3.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose, covering different file operations (compress, convert, extract, merge, split, etc.) and billing management. No two tools overlap in functionality.

Naming Consistency4/5

Most tool names follow a verb_noun pattern (compress_image, protect_pdf), but a few deviate (images_to_pdf, list_supported_conversions) causing minor inconsistency. The pattern is largely predictable.

Tool Count4/5

17 tools is slightly above the typical well-scoped range, but still reasonable given the breadth of file manipulation and billing operations. Each tool serves a distinct need.

Completeness4/5

The file conversion and PDF manipulation operations are well-covered (compress, convert, extract, merge, split, protect, etc.). The billing tools are complete for subscription and credit management. Minor gaps exist, such as batch operations or image format conversions.

Resources

Need Help?