Excel MCP Server

List workbooks

list_workbooks

Read-onlyIdempotent

Retrieve Excel files from a directory with their paths and sizes in bytes, optionally scanning subfolders, to inventory workbooks for processing or reporting.

Instructions

List Excel files in a directory: path to size in bytes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_workbooks"
  }
}

Input Schema

Name	Required	Description	Default
`directory`	No	Default: the first workbook directory (base of relative paths).
`recursive`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv2.0.0Oct 13, 2026

changedInput schema / properties / directory / description

Previous value: -"Directory to search. Leave empty for the server's workbook directory; otherwise use an absolute path."New value: +"Default: the first workbook directory (base of relative paths)."

removedInput schema / properties / directory / title
```
Removed value: -"Directory"
```
removedInput schema / properties / recursive / default
```
Removed value: -false
```
removedInput schema / properties / recursive / description
```
Removed value: -"Also search subdirectories."
```
removedInput schema / properties / recursive / title
```
Removed value: -"Recursive"
```

removedInput schema / title

Removed value: -"list_workbooksArguments"

removedOutput schema / $defs

Removed value: -{
-  "WorkbookFile": {
-    "properties": {
-      "path": {
-        "title": "Path",
-        "type": "string"
-      },
-      "size_bytes": {
-        "title": "Size Bytes",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "path",
-      "size_bytes"
-    ],
-    "title": "WorkbookFile",
-    "type": "object"
-  }
-}

addedOutput schema / additionalProperties
```
Added value: +{
+  "type": "integer"
+}
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "items": {
-      "$ref": "#/$defs/WorkbookFile"
-    },
-    "title": "Result",
-    "type": "array"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
removedOutput schema / title
```
Removed value: -"list_workbooksOutput"
```

Addedv1.1.1Sep 29, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare this a safe, read-only, idempotent, non-destructive, closed-world operation, so the safety profile is fully covered. The description adds the result shape ('path to size in bytes'), but says nothing about how recursion affects scope or what happens when the directory is empty or invalid.

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?

A single front-loaded sentence with no filler. The phrasing 'path to size in bytes' is slightly clipped, but no sentence is wasted.

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 an output schema present, return values need not be explained, and annotations cover the safety profile. However, the undocumented 'recursive' parameter and absent usage context leave the definition at bare minimum viability for a discovery tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: 'directory' is documented in the schema but 'recursive' is not, and the description does not compensate by explaining what recursion does or its default. The description adds essentially no parameter meaning beyond what the schema already states.

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 ('List Excel files in a directory') and even hints at the return shape. It is clearly distinguishable from siblings like create_workbook or describe_workbook, though it never names an alternative to differentiate explicitly.

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 guidance on when to use this versus describe_workbook, read_range, or other discovery tools, nor any prerequisites or exclusions. The agent must infer appropriate usage from the name alone.

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