Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco

pdf_to_xls

Convert PDF and scanned images to Excel XLS format. OCR extracts tables from document URLs for spreadsheet output.

Instructions

Convert PDF and scanned images to XLS (Excel 97-2003) format.
Ref: https://developer.pdf.co/api/pdf-to-excel/xls.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)
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. It only states the conversion objective, omitting important behavioral details such as API key requirements, asynchronous job processing, OCR behavior, or how to retrieve the output. The reference link is not a substitute for in-description disclosure.

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?

The description is a single sentence with a reference link, making it extremely concise and front-loaded. Every word serves a purpose, and no redundant information is included.

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?

With 11 parameters, no output schema, and no annotations, the description is underspecified. It lacks crucial context about output format, job completion, error handling, and required credentials, making it insufficient for an agent to invoke the tool correctly without external documentation.

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 provides descriptions for all 11 parameters, achieving 100% coverage. The description adds no additional parameter context beyond what the schema already states, so the baseline score of 3 is appropriate.

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 converts PDFs and scanned images to XLS (Excel 97-2003) format, a distinct output versus siblings like pdf_to_xlsx or pdf_to_csv. The verb 'Convert' and resource/format specificity make the purpose unambiguous.

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 does not explicitly say when to use this tool versus alternatives like pdf_to_xlsx. The distinction is implied by the output format name, but there is no explicit guidance on choosing this tool or exclusions.

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