MCP server for Google Drive file operations including read, write, search, and sharing management
gdrive-mcp has well-structured tool definitions with consistent naming (verb_noun pattern: drive_get, drive_search, drive_list, etc.) and complete input schemas using Zod validation. All 13 tools have descriptions and typed parameters. However, descriptions are often terse (10-50 chars), lacking context on WHEN to use each tool or dependencies between them. Parameter descriptions are minimal, many lack guidance on valid ranges, formats, or mutual exclusivity. Output schemas are not documented in the tool definitions. Error handling is present but generic. Security is strong (no secrets in params, OAuth2 server-side). Composition is good: tools are single-purpose and chainable via IDs.
Copy a file, optionally renamed into another folder
Create a folder
Trash a file by default; permanent delete needs double opt-in
Export a Workspace file to an explicit MIME type
Get file metadata by ID
List files in a folder (root when omitted)
List Shared Drives
Output schemas not documented. Tool definitions lack return type documentation, forcing LLMs to infer response structure. This breaks downstream tool chaining and wastes tokens on discovery.
Parameter descriptions lack actionable constraints. 'pageSize' says '1-100, default 20' but no description explains why or when to adjust. 'fields' in drive_get has no guidance on valid field names or format.
Mutual exclusivity not documented. drive_upload and drive_update both have contentText XOR contentBase64, but descriptions don't explicitly state 'mutually exclusive' or guide LLM on when to use each.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | <=2025-11-25 | v2 |
Move a file by adding/removing parents
List, create, or delete sharing permissions (user/group only at v1)
Read file content; Workspace files auto-export; large content truncates with nextOffset
Search Drive files with a Drive query string
Update file metadata and/or content
Upload a new file (contentText XOR contentBase64)
Tool descriptions too terse. 'Get file metadata by ID' (24 chars) and 'List files in a folder' (22 chars) lack context on WHEN to call vs similar tools or what fields are returned. Baseline is 194 chars.
Error handling generic. No recovery guidance in tool definitions. If drive_search fails, LLM doesn't know whether to retry, adjust query, or call a different tool.