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

Search Docs

search_docs
Read-onlyIdempotent

Find Google Docs by name across Drive or shared drives, returning paginated results so you can locate the right document quickly.

Instructions

Searches for Google Docs by name using Drive API (mimeType filter).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesText to search for in document names.
corporaNoCorpus to search ('user', 'domain', 'drive', 'allDrives'). Defaults to 'drive' when drive_id is set, otherwise 'allDrives'.
drive_idNoOptional shared drive ID to search.
page_sizeNoMaximum number of documents to return. Defaults to 10.
page_tokenNoPage token from a previous response's nextPageToken to retrieve the next page of results.
user_google_emailYesThe user's Google email address.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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": "Optional shared drive ID to search.",
+  "type": "string"
+}
    • addedInput schema / properties / page_size / description
      Added value: +"Maximum number of documents to return. Defaults to 10."
    • addedInput schema / properties / page_token
      Added value: +{
+  "default": null,
+  "description": "Page token from a previous response's nextPageToken to\nretrieve the next page of results.",
+  "type": "string"
+}
    • addedInput schema / properties / query / description
      Added value: +"Text to search for in document names."
    • addedInput schema / properties / user_google_email / description
      Added value: +"The user's Google email address."
  2. Changed8 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / page_size / title
      Removed value: -"Page Size"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / service
      Removed value: -{
-  "title": "service",
-  "type": "string"
-}
    • removedInput schema / properties / user_google_email / title
      Removed value: -"User Google Email"
    • changedInput schema / required
      Previous value: -[
-  "service",
-  "user_google_email",
-  "query"
-]New value: +[
+  "user_google_email",
+  "query"
+]
    • removedInput schema / title
      Removed value: -"search_docsArguments"
    • 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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds the mechanism (Drive API mimeType filter) but says nothing about pagination behavior or result limits beyond what the schema states.

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?

A single front-loaded sentence with zero filler; the resource and scope appear immediately.

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 rich annotations and an output schema, the safety and return-value burdens are lifted, but the description still omits sibling differentiation and pagination context, leaving the agent to infer when this tool beats search_drive_files.

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 the schema already documents all six parameters including corpora defaults and page_size. The description adds no parameter-level detail, which is the expected baseline when the schema does the heavy lifting.

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 (Searches) and resource (Google Docs) with a scope qualifier (by name), and the mimeType filter note clarifies it targets Docs specifically. It does not, however, explicitly distinguish itself from the sibling search_drive_files, which also searches Drive.

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 when-to-use guidance and no mention of alternatives such as search_drive_files or list_docs_in_folder. The agent must infer the selection criteria entirely from the name and description.

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