Skip to main content
Glama
formfeed

formfeed

Official

Turn PDF pages into pictures

pdf_to_image

Convert PDF pages to PNG or JPEG images to preview a page before redacting, create thumbnails, or render up to 100 pages at once. Returns a single image or a ZIP named by page.

Instructions

Draws pages of a PDF as PNG or JPEG pictures and returns the render with download_url: one page gives the picture, which this tool also hands back so you can look at it (up to 2 MB), several pages a ZIP of pictures named by page. At most 100 pages and 120 million pixels a call, about 13 A4 pages at 300 dpi. Use it to see a page before redact_pdf, or for thumbnails. Pass exactly one PDF: source, a render or library file of the workspace; path, a file on this machine; or file_base64. Starter plan and above; one unit per picture on a live key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_to_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpiNoResolution, 36 to 300, 150 when left out; at 72 a pixel stands for a point
pathNoAbsolute path of a PDF on this machine, up to 100 MB; sent with the request and not kept
pagesNoThe pages to draw, such as 1, 1-3,5 or 2- (page 2 to the last); every page when left out
formatNopng (the default) or jpg
sourceNoA PDF of the workspace: the rnd_ id of a PDF render, or a PDF of the file library by name (such as terms.pdf) or fil_ id
qualityNoJPEG quality, 1 to 100; ignored for PNG
filenameNoName of the file behind download_url; the source's name when left out
file_nameNoName of the PDF given as file_base64 or path, e.g. contract.pdf; the results are named after it
file_base64NoThe PDF itself, base64 encoded, up to 20 MB; sent with the request and not kept

Output Schema

NameRequiredDescriptionDefault
idYesrnd_ id of the render
formNoWhat fill_pdf_form did: the fields filled, those left out (unknown name or invalid value) and those whose calculation or display format no viewer ran
pdfaNoThe PDF/A verdict (PDF/A-2b or PDF/A-3b), when the template declares it
errorYesWhy a failed render failed
unitsYesUnits the render counted
outputNoThe format of the file: pdf, png, jpg, webp, docx or pptx, or zip for the several files of split_pdf and pdf_to_image
statusYes
einvoiceNoThe e-invoice report, when the render made one
templateYesThe template and version rendered; null for html and conversions
expires_atYesWhen download_url stops working; get_render issues a fresh one
page_countYes
environmentYes
download_urlYesSigned link to the file; null until the render succeeded
accessibilityNoThe PDF/UA-1 verdict, when the template declares it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.26

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, not idempotent), the description discloses the inline 2 MB image return, the ZIP fallback for multiple pages, hard limits of 100 pages / 120M pixels per call, the plan requirement ('Starter plan and above'), and unit billing ('one unit per picture on a live key'). It also states that path and file_base64 payloads are not retained server-side, which is exactly the kind of behavior an agent must know before sending data.

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?

Purpose, output shape, limits, usage hint, input exclusivity, and billing are all packed into one front-loaded paragraph with no filler. It is dense to the point of being slightly run-on in the first sentence, which keeps it just under top marks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter conversion tool with an output schema, the description covers what an agent needs to call it correctly: which input selector to use, size limits, plan/billing prerequisites, and what comes back in each case. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns an extra point by stating the mutual-exclusion rule 'Pass exactly one PDF: source... path... or file_base64', a constraint the schema does not express with any oneOf/anyOf. It does not add dpi, quality, or filename semantics beyond the schema, so it is not a 5.

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 specific verb and resource ('Draws pages of a PDF as PNG or JPEG pictures') and immediately specifies the output shape (a single picture or a ZIP of pictures named by page). The format options and page selection are concrete enough that an agent can distinguish this from siblings like render, get_render, or compress_pdf without opening any schema.

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?

'Use it to see a page before redact_pdf, or for thumbnails' gives a concrete motivating scenario and names a related sibling as a downstream step. There is no explicit when-not guidance (e.g., use get_pdf_info instead if you only need metadata), so it stops short of 5.

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