Skip to main content
Glama

Convert PDF to JPG

pdf_to_jpg
Idempotent

Turn every page of your PDFs into a JPG image, at the resolution you need. Returns a link to download the result (kept about an hour). Credits on paid plans: 2 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": "pdf_to_jpg"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpiNoResolution Values: '96' = 96 dpi (screen, light); '150' = 150 dpi; '300' = 300 dpi (print)150
filesYesInput files (.pdf). 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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag openWorldHint=true and destructiveHint=false, but the description adds behavior those annotations cannot express: the result is a download link with roughly one-hour retention and the operation costs 2 credits per page on paid plans. It omits a few useful traits, such as whether credits are consumed on failed conversions or any maximum page limit per request.

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?

Three short sentences lead with the core transformation, then the return artifact, then the cost — each sentence carries distinct, non-redundant information. No filler or repetition of the schema.

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 explains the return value (a downloadable link) and its expiry, and it discloses the per-page credit cost. It is nearly complete for a two-parameter conversion tool, though it could mention limits on total pages or file size handling beyond what the schema states.

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 coverage is 100%, including full enum explanations for dpi and the url/name/content_base64 input variants, so the baseline is 3. The description only mirrors the resolution choice with 'at the resolution you need' and adds no format or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition gives a specific verb and resource ('Turn every page of your PDFs into a JPG image') plus the per-page output granularity, which is enough to tell it apart from the inverse jpg_to_pdf sibling. It stops short of explicitly naming which sibling handles the opposite direction or related conversions, so it is clear but not maximally differentiated.

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 only implied by the purpose statement — an agent can infer this is for rasterizing PDF pages into images, but there is no explicit 'use this when...' framing and no exclusion such as choosing jpg_to_pdf for the reverse case or ocr_pdf when text extraction is needed. Adequate but leaves routing to inference.

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