Google Drive
Create, find, export, share and comment on Google documents.
Connect a Google account to manage documents as files: generate one from markdown or from a template with its placeholders filled, overwrite a generated document's body, search the documents this connection has created, export to PDF or Word, read and post comments, and share. Runs on Google's per-file Drive scope, so tools reach documents created through this connection - for editing the CONTENT of any document (including pre-existing ones), use the Google Docs integration.
Connect
Sign in with Google. Sign in with Google to create, find, export, share and comment on documents. An organization admin configures the OAuth app once under Integrations → OAuth apps; after that, connecting is a consent screen.
-
Connecting signs in as YOU. Drive access is the per-file tier (drive.file): tools reach documents created through this connection - never the rest of your Drive.
-
The connection also asks for Docs access because filling a template's placeholders happens through the Docs API.
Tools
| Tool | Access | What it does |
|---|---|---|
Search documents (yekar.google-drive.search) | Read | Find Google Docs created through this connection, by title or content. Returns document ids the other tools take. Paginated. Cannot see the rest of the account's Drive (per-file scope) - for a pre-existing document, ask the user for its link instead. |
Create document (yekar.google-drive.create) | Write | Create a Google Doc, optionally with its whole body written from markdown. NOT idempotent: a retried call creates a SECOND document, so after an interruption the run fails rather than leave a duplicate behind. |
Copy from template (yekar.google-drive.copy-from-template) | Write | Copy a template document and fill its placeholders in one step - the usual way to generate a contract, report or letter. The template must be a document created through this connection (per-file Drive scope). NOT idempotent: a retried call produces a SECOND copy. |
Replace document body (yekar.google-drive.replace-body) | Write | Overwrite a document's whole content from markdown, keeping its id, URL and sharing. Only works on documents created through this connection (per-file Drive scope). Idempotent - rewriting the same document with the same markdown converges, so it is the recovery-safe way to write a generated document. Comments and suggestions anchored to the old text do not survive. |
Export document (yekar.google-drive.export) | Read | Export a document created through this connection (per-file Drive scope) to PDF, Word (docx), ODT, RTF, plain text, markdown, EPUB, or HTML. The file is saved as an attachment on this session rather than returned inline. |
Share document (yekar.google-drive.share) | Write | Grant a person, group, domain, or anyone-with-the-link access to a document created through this connection (per-file Drive scope). By default no notification email is sent - set sendNotificationEmail to tell the grantee. |
Comment on document (yekar.google-drive.comment) | Write | Start a comment thread on a document created through this connection (per-file Drive scope), as the signed-in user. The comment applies to the document as a whole - Drive's API cannot anchor a new comment to a specific passage. NOT idempotent: a retried call posts a second comment. |
List comments (yekar.google-drive.list-comments) | Read | Read the comment threads on a document created through this connection (per-file Drive scope), with their replies and the text each one is anchored to. Each thread carries its own resolved flag - Drive has no server-side filter for it, and dropping resolved threads here would silently shrink a page below the size that was asked for. |
Notes
- Sign in with Google to connect - tools act as your Google account, scoped to files created through this connection.
- Search only finds documents this connection created. For a pre-existing document, ask the user to paste its link and use the Google Docs integration to read or edit it.
- To fill a template use Copy from template - it needs no indexes and fills every placeholder in one atomic step.
- Replace document body is the recovery-safe way to write a generated document: same markdown in, same document out.