Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco

excel_to_json

Converts Excel XLS/XLSX files to JSON format. Specify file URL and optional worksheet index.

Instructions

Convert Excel(XLS, XLSX) to JSON.
Ref: https://developer.pdf.co/api-reference/convert-from-excel/json.md

Input Schema

TableJSON 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.
httpusernameNoHTTP auth user name if required to access source url. (Optional)
httppasswordNoHTTP auth password if required to access source url. (Optional)
nameNoFile name for the generated output. (Optional)
worksheetIndexNoIndex of the worksheet to convert. (Optional)
api_keyNoPDF.co API key. If not provided, will use X_API_KEY environment variable. (Optional)

Implementation Reference

  • Helper service function that constructs and dispatches the API request 'xls/convert/to/json' using the PDF.co HTTP client.
    async def convert_to(
        _from: str, _to: str, params: ConversionParams, api_key: str | None = None
    ) -> BaseResponse:
        return await request(f"{_from}/convert/to/{_to}", params, api_key=api_key)
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It fails to disclose behavioral traits such as handling of multiple worksheets, file size limits, or authentication nuances beyond the schema. Only a brief conversion statement is given.

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 short (two sentences including a reference link), which is concise but may be too minimal. It is front-loaded with the core action but lacks structure to cover additional details like output format.

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 6 parameters and no output schema, the description fails to explain what the JSON output looks like (e.g., structure, handling of multiple worksheets). A complete description would provide this context, but it is missing.

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 extra meaning beyond the schema; e.g., 'worksheetIndex' is left to the schema's minimal 'Index of the worksheet to convert' without clarification on indexing or default behavior.

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?

The description clearly states the verb 'Convert' and the resource 'Excel(XLS, XLSX)' to 'JSON', distinguishing it from sibling Excel converters (e.g., excel_to_csv). However, it does not specify scope (e.g., single worksheet vs entire workbook), which could add clarity.

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 use this tool versus alternatives like excel_to_csv or pdf_to_json. The description lacks context about use cases or prerequisites, leaving the agent without decision support.

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