Skip to main content
Glama
taylorwilsdon

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

by taylorwilsdon
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

List Spreadsheets

list_spreadsheets
Read-onlyIdempotent

List Google Drive spreadsheets accessible to a specified user email. Limit the result count to quickly locate the spreadsheet you need.

Instructions

Lists spreadsheets from Google Drive that the user has access to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoMaximum number of spreadsheets to return. Defaults to 25.
user_google_emailYesThe user's Google email address. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / max_results / description
      Added value: +"Maximum number of spreadsheets to return. Defaults to 25."
    • removedInput schema / properties / max_results / title
      Removed value: -"Max Results"
    • removedInput schema / properties / service
      Removed value: -{
-  "title": "service",
-  "type": "string"
-}
    • addedInput schema / properties / user_google_email / description
      Added value: +"The user's Google email address. Required."
    • removedInput schema / properties / user_google_email / title
      Removed value: -"User Google Email"
    • changedInput schema / required
      Previous value: -[
-  "service",
-  "user_google_email"
-]New value: +[
+  "user_google_email"
+]
    • removedInput schema / title
      Removed value: -"list_spreadsheetsArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds a scoping constraint ('user has access to'), which is useful context. However, it does not elaborate on pagination or output behavior beyond what the schema provides, so the added behavioral insight is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundancy. It efficiently conveys the essential information without any filler or extraneous details.

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

Completeness4/5

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

For a simple read-only listing operation with complete schema coverage, annotations, and an output schema, the description sufficiently covers the core functionality. However, the absence of any mention of related tools or potential limitations makes it not fully complete in the broader context of many similar Drive-related tools.

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%, meaning both parameters (max_results, user_google_email) already have descriptions in the schema. The tool description does not add any additional semantics or usage details for the parameters, so the baseline score of 3 applies.

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?

The description uses a specific verb ('lists') and clearly identifies the resource ('spreadsheets from Google Drive') and scope ('that the user has access to'). This differentiates it from sibling tools like get_spreadsheet_info or read_sheet_values which target specific spreadsheets or data.

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?

The description provides no guidance on when to use this tool versus alternatives like list_drive_items or search_drive_files. There are no exclusions or explicit mentions of suitable contexts, leaving the agent without decision support for tool selection.

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/taylorwilsdon/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server