Reading and writing the contents of a file is only half of file work. The other half is everything around the file: putting the finished report in the right folder, filing this month's invoices, copying a template before working on it, sharing a result with the person who asked for it, finding the file in the first place.
Agents can do all of that, in Google Drive and in OneDrive and SharePoint.
The pattern: go to the folder, then act
Most drive operations apply to the folder or file the agent currently has open. So the natural instruction is a navigational one: open the 2026 Invoices folder, then upload the signed copy there.
This is the same model as the file-content tools, and it has the same benefit — there is no "which folder" argument for the agent to get wrong, and you can see from the run exactly where it went.
The exception is searching, which is global: an agent can search a drive without navigating anywhere first.
Google Drive
Operation | Tool | Notes |
Create a folder |
| Nested paths work — a name like |
Move files into a folder |
| Moves one or more files, optionally renaming them |
Copy a file into a folder |
| The usual way to work on a copy and leave the original alone |
Upload an existing file into a folder |
| Takes a file the agent already has — a generated PDF, a fetched attachment — and puts it in the open folder under a chosen name |
Get file or folder details |
| Name, type, location, and other metadata |
Share a file |
| Grants access to a person, a group, a domain, or anyone, as reader, commenter, or writer, with an optional notification message |
Search the drive |
| Search by name, by text inside the file, by file type, or within a particular folder — and combine those criteria |
OneDrive and SharePoint
Operation | Tool | Notes |
Create a folder |
| In OneDrive or in a SharePoint site's document library |
Upload a file |
| Puts a file into the open folder |
Move a file |
| Moves a file to another folder |
Find recently modified files |
| Finds files of a given type, modified after a given date, anywhere the account can see — including files other people have shared |
find_recently_modified is worth calling out. It answers a question that comes up constantly — "has anything new landed?" — without anyone having to know where the file lives, and it covers shared files as well as the account's own. Two caveats: it needs a Microsoft 365 work or school account (personal Microsoft accounts are not supported), and it reads Microsoft's search index, which lags live edits by roughly 15 to 60 minutes. An empty result means "not indexed yet", not "does not exist".
Tools that stay off until you turn them on
Three of these tools are disabled by default and have to be enabled deliberately by the thunk author: share_file, google_drive_search, and find_recently_modified.
They are treated differently because of their reach. Sharing changes who can see a document. The two search tools look across everything the connected account can read, rather than at one file the workflow already knows about. That is a broader capability than most steps need, so it is opt-in rather than automatic.
Everything else about tool availability works as usual: tools can be turned on and off for the thunk, and each step can decide which of them it is allowed to use. Files themselves stay governed by the drive's own permissions — an agent acts with the identity behind the connection and can never reach a file that identity cannot. See User Identity During Agent Execution.