Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Spreadsheets

list_spreadsheets
Read-onlyIdempotent

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

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corporaNoCorpus to search ('user', 'domain', 'drive', 'allDrives'). Defaults to 'drive' when drive_id is set, otherwise 'allDrives'.
drive_idNoShared drive ID to search.
page_tokenNoPage token from a previous response's nextPageToken to retrieve the next page of results.
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.

  1. Changed3 schema fields changedv1.30.1
    • addedInput schema / properties / corpora
      Added value: +{
+  "default": null,
+  "description": "Corpus to search ('user', 'domain', 'drive', 'allDrives').\nDefaults to 'drive' when drive_id is set, otherwise 'allDrives'.",
+  "type": "string"
+}
    • addedInput schema / properties / drive_id
      Added value: +{
+  "default": null,
+  "description": "Shared drive ID to search.",
+  "type": "string"
+}
    • addedInput schema / properties / page_token
      Added value: +{
+  "default": null,
+  "description": "Page token from a previous response's nextPageToken to retrieve the next page of results.",
+  "type": "string"
+}
  2. 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
+}
  3. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the 'user has access to' scoping note; it says nothing about pagination behavior, result caps, or how Drive permissions affect what is returned.

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?

One short sentence with no filler, and the resource is front-loaded. It is efficient, though its brevity comes at the cost of the guidance a listing tool with five parameters arguably warrants.

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 and annotations carrying the safety profile, the description does not need to explain return values. Still, for a Drive-listing tool with a rich sibling set, the absence of any routing or scope detail (shared drives, corpora) leaves a gap.

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%, and the schema documents every parameter including corpora, drive_id, page_token, max_results, and user_google_email with defaults and enum-like values. The description adds no parameter meaning beyond that, so the baseline of 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?

The description states a specific verb (Lists) and resource (spreadsheets from Google Drive), plus a scope qualifier ('that the user has access to'). However, it does nothing to distinguish itself from near-siblings like list_drive_items, search_drive_files, or list_docs_in_folder, so an agent must infer the boundary from names alone.

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 statement of when to use this tool versus alternatives such as search_drive_files (query-based discovery) or list_drive_items (general Drive listing). The agent gets no exclusions, prerequisites, or selection criteria.

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