Skip to main content
Glama
Sign In
PDF.co MCP Server

PDF.co MCP Server

Official
by pdfdotco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

excel_to_csv

Convert XLS or XLSX spreadsheets to CSV from a source file URL, so tabular data can be reused in CSV-based workflows. Supports choosing a worksheet and setting an output link lifetime.

Instructions

Convert Excel(XLS, XLSX) to CSV.
Retiring on January 5, 2027: the underlying PDF.co API endpoint is being discontinued. The tool keeps working until that date and will be removed afterwards.
Ref: https://developer.pdf.co/api/convert-from-excel/csv.md

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "excel_to_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to the source file (XLS, XLSX). Supports publicly accessible links including Google Drive, Dropbox, PDF.co Built-In Files Storage. Use 'upload_file' tool to upload local files.
nameNoFile name for the generated output. (Optional)
api_keyNoPDF.co API key. If not provided, will use X_API_KEY environment variable. (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)
worksheetIndexNoIndex of the worksheet to convert. (Optional)

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

B3.2/5.0
Behavior3/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 does disclose a genuinely useful behavioral trait — the API endpoint retirement on January 5, 2027 — which is non-obvious and important for an agent choosing tools. However it says nothing about authentication, whether the call is synchronous or returns a job, rate limits, or what the response contains (presumably a link).

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 core action is front-loaded in the first sentence, and the retirement warning plus doc link are compact and relevant. Nothing is padded, though the raw URL line could be folded into the warning sentence.

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

Completeness3/5

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

With no output schema, the description should say what the call returns — presumably a CSV output link subject to the expiration parameter — but it does not. Parameters are fully covered by the schema, and the deprecation notice is a plus, leaving the return-value gap as the main deficiency.

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 every one of the 8 parameters is documented in the schema, including url sourcing, api_key fallback, profiles, expiration, and worksheetIndex. 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 and resource pair ('Convert Excel(XLS, XLSX) to CSV') including the input formats accepted. Sibling tools like excel_to_json, excel_to_html, and excel_to_txt are distinguished only implicitly by the named output format; no explicit differentiation is given.

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?

No guidance on when to choose this over excel_to_json/excel_to_xml/excel_to_html or pdf_to_csv, and no prerequisites stated. The only contextual note is the retirement date, which is about lifecycle, not usage.

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