Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco

pdf_to_image

Convert PDF files and scanned documents to JPG, PNG, WebP, or TIFF images. Extract specific pages or ranges for quick previews, sharing, or embedding.

Instructions

Convert PDF and scanned images to various image formats (JPG, PNG, WebP, TIFF).
Ref:
 - https://developer.pdf.co/api/pdf-to-image/jpg.md
 - https://developer.pdf.co/api/pdf-to-image/png.md
 - https://developer.pdf.co/api/pdf-to-image/webp.md
 - https://developer.pdf.co/api/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.
langNoLanguage for OCR for scanned documents. Default is 'eng'. See PDF.co docs for supported languages. (Optional, Default: 'eng')eng
nameNoFile name for the generated output. (Optional)
rectNoDefines coordinates for extraction (e.g., '51.8,114.8,235.5,204.0'). (Optional)
typeNoType of image to convert to. (jpg, png, webp, tiff) (Optional)jpg
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)
api_keyNoPDF.co API key. If not provided, will use X_API_KEY environment variable. (Optional)
passwordNoPassword of the PDF file. (Optional)
httppasswordNoHTTP auth password if required to access source url. (Optional)
httpusernameNoHTTP auth user name if required to access source url. (Optional)
line_groupingNoEnables line grouping within table cells when set to '1'. (Optional)0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It hints at OCR via 'scanned images' but omits key behaviors such as output file generation, OCR language handling, password/HTTP auth support, page selection, and line grouping. The external references do not compensate for missing inline transparency.

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?

The description is concise and front-loaded with a clear main sentence, followed by documentation links. While the references are useful, they are not inline guidance, but the overall structure is efficient and free of fluff.

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?

This is a complex 12-parameter tool with no annotations and no output schema, yet the description only provides a basic conversion statement plus doc links. It lacks critical context about OCR, page selection, authentication, and expected output, making it insufficient for an agent to fully grasp the tool's capabilities.

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?

The input schema already describes all 12 parameters with 100% coverage, so the baseline is 3. The description adds no parameter-specific meaning beyond naming the output formats, which are already enumerated in the 'type' choices.

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 uses a specific verb ('Convert') and clearly identifies the resource ('PDF and scanned images') and output formats ('JPG, PNG, WebP, TIFF'), which distinguishes it from sibling conversion tools like pdf_to_text and pdf_to_json. The purpose is immediately clear and not a tautology.

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?

The description implies usage when converting PDFs to raster image formats, but it does not explicitly state when to choose this tool over alternatives or mention exclusions. It lacks direct guidance like 'use this for image output rather than pdf_to_text'.

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