Skip to main content
Glama

List spreadsheets

spreadsheet_list
Read-only

List the spreadsheets one of your Google Sheets, Excel or Smartsheet account connections can read (postgres_list_connections marks them spreadsheets: true), or one spreadsheet's tabs. Without spreadsheetId it returns the files: for a Google account, the spreadsheets its owner chose for OrionBI with "Add spreadsheets" on the Workbooks page (Google lets OrionBI open nothing else); for a Microsoft 365 account, the Excel workbooks it can open across OneDrive and SharePoint, filtered by query; for a Smartsheet account, the sheets it can open, filtered by query. With spreadsheetId (and, for Excel, driveId) it returns that file's tabs and their sizes; a Smartsheet sheet is one table, its columns named by their titles. For Excel, link instead takes a OneDrive or SharePoint sharing link the user pasted and returns that workbook and its worksheets. Excel connections read workbooks (.xlsx, .xlsm) in OneDrive for Business and SharePoint, not personal OneDrive. Every file and tab carries selection, the JSON object to pass as sql to dataset_create, which turns a tab into a Data Set with typed columns (numbers, dates, true/false) refreshed on a schedule. If a Google spreadsheet the user names is not listed, ask them to add it on the Workbooks page; it cannot be reached any other way.

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": {
      "connection": "<connection>"
    },
    "name": "spreadsheet_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkNoExcel only: a OneDrive or SharePoint link to a workbook, as the user pasted it. Returns that workbook and its worksheets.
queryNoOnly files whose name matches this. For Excel it is a search across OneDrive and SharePoint; for Smartsheet, sheets whose name contains it.
driveIdNoExcel only: the file's `driveId` from an earlier call.
connectionYesName of a Google Sheets, Excel or Smartsheet account connection you own.
spreadsheetIdNoList this file's tabs instead of the files: a `fileId` from an earlier call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses real operational limits: Google only returns spreadsheets explicitly added via the Workbooks page, Excel reads OneDrive for Business and SharePoint but not personal OneDrive, and Smartsheet exposes one table with columns named by title. It also describes the returned `selection` object and how it feeds a scheduled, typed Data Set, which annotations alone could never convey.

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 purpose and no-argument behavior are front-loaded, and nearly every sentence carries provider-specific information that is not available elsewhere. Some sentences are long and pack several clauses (the Google/Microsoft/Smartsheet enumeration), which slows parsing slightly, but there is no filler.

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

Completeness5/5

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

For a five-parameter, multi-provider, open-world listing tool with no output schema, the definition covers discovery of the connection, both return modes, the returned `selection` payload, and the handoff to `dataset_create`. An agent has everything needed to pick the right parameters and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning on top: `spreadsheetId` is clarified as a `fileId` from an earlier call, `driveId` is scoped to Excel, and `link` is explained as taking a link the user pasted rather than an ID. It also explains that `query` behaves as a search across OneDrive/SharePoint for Excel but a name-contains filter for Smartsheet.

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?

States a specific verb and resource ("List the spreadsheets... or one spreadsheet's tabs") and immediately names the three provider types it spans. It also distinguishes the two operating modes (files vs. tabs) in the first two sentences, so an agent can tell exactly what comes back before opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is given for every mode: without `spreadsheetId` you get files, with it (plus `driveId` for Excel) you get tabs, and `link` handles a pasted OneDrive/SharePoint sharing URL. It even names the sibling that reveals which connections are usable (`postgres_list_connections` marks them `spreadsheets: true`) and the follow-on tool (`dataset_create`), plus an escalation path when a Google file is missing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources