Google Drive
Enable agents to manage files in Google Drive. Upload, download, share, and organize files and folders.
Available Tools
11 tools available in this integration
GoogleDrive.WhoAmI Get comprehensive user profile and Google Drive environment information
GoogleDrive.GetFileTreeStructure Get the file/folder tree structure of the user's Google Drive
GoogleDrive.GenerateGoogleFilePickerUrl Generate a Google File Picker URL for user-driven file selection
GoogleDrive.SearchFiles Search for files in Google Drive
GoogleDrive.CreateFolder Create a new folder in Google Drive
GoogleDrive.RenameFile Rename a file or folder in Google Drive
GoogleDrive.MoveFile Move a file or folder to a different folder
GoogleDrive.DownloadFile Download a blob file from Google Drive as base64 encoded content
GoogleDrive.DownloadFileChunk Download a specific byte range of a file from Google Drive
GoogleDrive.UploadFile Upload a file to Google Drive from a URL
GoogleDrive.ShareFile Share a file or folder in Google Drive with specific people
Why agent-optimized tools matter
Built for intent, not API schemas
Forcing the agent to juggle not only what you want to get done, but also how to operate all the APIs it needs to use is a recipe for disaster. Agent-optimized tools keep the agent focused on the work at hand, not ID hunting.
Up to 100x fewer tokens
Context bloat is a serious problem that gets in the way of real work getting done with agents. Agent-optimized tools return only the fields the agent needs to get the job done, not the full API response. Up to 100x less token consumption on every call.
Coverage for the whole task
Most tasks take more than one action to finish. Agent-optimized tools cover the full sequence so the agent completes the workflow end to end, not just the first lookup.
Consistent at scale
Agent-optimized tools behave the same across every user, every run, every harness, every model, and every effort level. No need for the agent to spend time and tokens re-learning the API shape, it can focus on the task at hand. What works for one user holds up when serving thousands in production.
Your questions, answered
It's built around what an agent is trying to accomplish rather than mirroring Google Drive's raw API. Fewer required parameters, far fewer tokens per call, and coverage for the whole task — so agents succeed more often.
Yes. The toolkit is exposed over an MCP gateway that any framework or MCP client can connect to, and we publish install guides for the editors and coding agents we document.
No. Arcade proxies API calls and does not persist your Google Drive content. Where Google Drive requires credentials, Arcade brokers them and stores them encrypted at rest — the model never sees them.
With Contextual Access policies: require human approval before consequential actions, redact sensitive fields on the way back, or restrict the scopes a given agent gets.
