Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pdf_to_xls

Convert PDF files and scanned images into XLS (Excel 97-2003) format using OCR for scanned documents, with options for page ranges, table regions, and languages.

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)
profilesNoExtra engine options for this endpoint as a JSON object encoded in a string. The options differ per endpoint; see https://developer.pdf.co/api/profiles. (Optional)
expirationNoLifetime of the output link in minutes; the output file is deleted afterwards. API default is 60; the maximum depends on the plan. (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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.0.11
    • addedInput schema / properties / expiration
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Lifetime of the output link in minutes; the output file is deleted afterwards. API default is 60; the maximum depends on the plan. (Optional)",
+  "title": "Expiration"
+}
    • addedInput schema / properties / profiles
      Added value: +{
+  "default": "",
+  "description": "Extra engine options for this endpoint as a JSON object encoded in a string. The options differ per endpoint; see https://developer.pdf.co/api/profiles. (Optional)",
+  "title": "Profiles",
+  "type": "string"
+}
  2. First observed

TDQS

C2.9/5.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 disclosure burden, and it discloses almost nothing beyond the format. It does not say whether the call is synchronous or job-based (siblings get_job_check/wait_job_completion suggest async), that the result is a downloadable link that expires, or that an API key is required. The only extra is a bare documentation URL.

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?

One front-loaded sentence plus a reference link, with zero filler. It is efficient, though efficiency here partly reflects how little was said rather than disciplined editing.

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 13-parameter conversion tool with no output schema and no annotations, and the description never explains what comes back (a link to the generated XLS file) or how the expiration parameter affects it. The format distinction that matters most against pdf_to_xlsx is implied but never made explicit, leaving real gaps for the calling agent.

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% and all 13 parameters are individually documented in the schema, including lang, pages, rect, and expiration. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb+resource pair ('Convert PDF and scanned images to XLS') and adds the useful qualifier that the target is Excel 97-2003 format, which is the main thing separating it from the sibling pdf_to_xlsx. However, it never names pdf_to_xlsx or pdf_to_csv as the alternatives, so an agent must infer the format distinction itself.

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?

There is no when-to-use guidance at all: no statement of when to pick this over pdf_to_xlsx (modern format) or pdf_to_csv, no prerequisites about the source file being publicly reachable or uploaded first, and no note that OCR only applies to scanned inputs. An agent gets only the bare conversion statement.

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

Deploy Server

Other Tools