Skip to main content
Glama

Convert JPG to PDF

jpg_to_pdf
Idempotent

Put photos, scans and screenshots (JPG, PNG, TIFF, WEBP…) into a single PDF, in the order you want and without losing quality. Returns a link to download the result (kept about an hour). Credits on paid plans: 1 per page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "files": "<files>"
    },
    "name": "jpg_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoPage size Values: 'a4' = A4; 'carta' = Letter; 'imagen' = Same as the imagea4
filesYesInput files (.bmp, .gif, .jfif, .jpe, .jpeg, .jpg, .png, .tif, .tiff, .webp). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).
marginNoMargin Values: 'no' = No margin; 'pequeno' = Small; 'grande' = Largeno

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false) by disclosing the returned download link's ~1 hour retention and the credit cost of 1 per page on paid plans. Missing details on failure behavior or maximum page count, but the cost and output-lifetime disclosures are exactly the kind of context annotations cannot carry.

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-loads the core action and format list, then tacks on the return-value and credit notes; every clause carries information. Slightly dense in a single run-on sentence, but no wasted words.

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?

With no output schema, the description correctly fills the gap by describing the return value (download link) and its lifetime, plus cost. A note on the ordering of files relative to the input array or on multi-page behavior would close the remaining gap, but an agent has enough to call it correctly.

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 files, size and margin are already fully documented including the enum meanings and the 20 MB base64 limit. The description adds only the ordering expectation for the files array, which is marginal beyond the schema; 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?

States a concrete verb+resource: putting JPG/PNG/TIFF/WEBP images into a single PDF, preserving quality and user-specified order. This unambiguously separates it from the reverse-direction sibling pdf_to_jpg and from collection tools like merge_pdf.

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?

Usage is implied by the input formats listed and by the 'in the order you want' hint about ordering semantics, but there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative (e.g., versus merge_pdf or word_to_pdf).

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.

Resources