Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco

pdf_to_image

Convert PDF and scanned documents to JPG, PNG, WebP, or TIFF images with optional page selection and OCR.

Instructions

Convert PDF and scanned images to various image formats (JPG, PNG, WebP, TIFF).
Ref:
 - https://developer.pdf.co/api-reference/pdf-to-image/jpg.md
 - https://developer.pdf.co/api-reference/pdf-to-image/png.md
 - https://developer.pdf.co/api-reference/pdf-to-image/webp.md
 - https://developer.pdf.co/api-reference/pdf-to-image/tiff.md

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to the source file. Supports publicly accessible links including Google Drive, Dropbox, PDF.co Built-In Files Storage. Use 'upload_file' tool to upload local files.
httpusernameNoHTTP auth user name if required to access source url. (Optional)
httppasswordNoHTTP auth password if required to access source url. (Optional)
pagesNoComma-separated page indices (e.g., '0, 1, 2-' or '1, 3-7'). Use '!' for inverted page numbers (e.g., '!0' for last page). Processes all pages if None. (Optional)
unwrapNoUnwrap lines into a single line within table cells when lineGrouping is enabled. Must be true or false. (Optional)
rectNoDefines coordinates for extraction (e.g., '51.8,114.8,235.5,204.0'). (Optional)
langNoLanguage for OCR for scanned documents. Default is 'eng'. See PDF.co docs for supported languages. (Optional, Default: 'eng')eng
line_groupingNoEnables line grouping within table cells when set to '1'. (Optional)0
passwordNoPassword of the PDF file. (Optional)
nameNoFile name for the generated output. (Optional)
typeNoType of image to convert to. (jpg, png, webp, tiff) (Optional)jpg
api_keyNoPDF.co API key. If not provided, will use X_API_KEY environment variable. (Optional)
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as API key requirements, rate limits, file size limits, or what happens on error. The external references contain this info but are not part of the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence plus links), but it is under-specified for a tool with 12 parameters. It lacks important context, making it somewhat inadequate.

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

Completeness2/5

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

Given the tool's complexity (12 parameters, no output schema, no annotations), the description is incomplete. It does not explain return values, handling of multiple pages, or processing behavior. External links are referenced but not inline.

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 baseline is 3. The description does not add any additional meaning beyond the schema for any of the 12 parameters.

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 clearly states the tool's purpose: converting PDFs and scanned images to image formats (JPG, PNG, WebP, TIFF). It specifies the resource and output, and naturally differentiates from sibling pdf_to_* tools that convert to non-image formats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool over alternatives like image_to_pdf or other conversion tools. There is no mention of context, prerequisites, or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pdfdotco/pdfco-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server