Official TaskKit MCP server for Google Drive file search, management, sharing, and content operations.
Server has 15 tools with complete input schemas and descriptions present for all tools and parameters. However, descriptions are often terse (10-30 chars) and lack actionable context for LLM selection. Tool names follow verb_noun convention well (search_files, get_file, create_file). Output schemas are not documented in the tool definitions, only inferred from test code. Error handling exists but lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear risk stratification in metadata. Parameter descriptions are minimal; many lack format/constraint details. No batch operations despite agents likely calling similar tools in loops.
Copy a file in Google Drive
Create a new file in Google Drive
Create a new folder in Google Drive
Delete a file from Google Drive
Get information about Google Drive storage and quota
ID of the file to retrieve
Get content of a file from Google Drive
Tool descriptions are too terse (10-40 chars). LLMs cannot determine when to select a tool vs. similar alternatives. E.g., get_file: 'ID of the file to retrieve' describes the parameter, not the tool. Should be: 'Retrieve metadata and optionally content for a specific file. Use when you have a file ID and need details like name, size, or permissions.'
No output schemas documented in tool definitions. Test code shows structuredContent with fields like 'files', 'content', 'credentials', but tool definitions do not declare what fields agents should expect. LLMs cannot plan downstream calls without knowing response structure.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk stratification in metadata. delete_file, share_file, and update_file should be marked destructive/write to guide agent caution and enable safety policies.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2025-06-18+ | v2 |
Get permissions for a file in Google Drive
Get revision history of a file in Google Drive
List files in Google Drive with pagination support
List shared drives accessible to the authenticated user
Move a file to a different folder in Google Drive
Search query for files in Google Drive
Share a file with users or groups in Google Drive
Update an existing file in Google Drive
Parameter descriptions lack format/constraint details. E.g., 'mimeType' in get_file_content has no guidance on valid values (text/plain, application/pdf, etc.). 'role' in share_file lists examples but no enum constraint. LLMs hallucinate invalid values without formal constraints.
Error handling in BaseToolHandler.handleGoogleApiError() returns generic error messages without recovery guidance. E.g., 'Google API Error: ...' tells agent nothing about whether to retry, ask user, or abandon. Should include: 'This error is retryable. Try again in 5 seconds.' or 'User lacks permission. Ask them to grant access.'