Google Docs
Service domainDOCUMENTS
Arcade Optimized
Arcade.dev LLM tools for Google Docs
13tools
9require secrets
Google Docs Toolkit
The Google Docs toolkit connects Arcade to Google Docs (and the Drive layer beneath it), enabling LLMs to create, read, edit, search, and comment on documents via the connected user's Google account.
Capabilities
- Document creation: Create blank documents or documents pre-populated with plain text or Markdown (with heading, bold, italic, and list formatting applied automatically).
- Reading and inspection: Retrieve documents as raw Google Docs API resources, as compact DocMD (with block IDs and character indices for precise editing), or as metadata-only summaries (title, ID, URL, tab structure, character counts).
- Structured editing and appending: Apply
batchUpdaterequests using DocMD indices for surgical edits, or append text to the end of a specific tab in a document. - Search: Query the user's accessible Drive for documents by keyword, returning either metadata or metadata plus main-body content.
- Comments: Post comments on documents (as the connected account, notifying collaborators) and list existing comments with text, replies, and author display names, paged for large documents.
- Access management and identity: Generate a Google Drive inline file-picker URL so users can grant the app access to specific files, and look up the connected account's profile (name, email, picture).
OAuth
This toolkit authenticates via OAuth 2.0 with Google. See the Arcade Google auth provider docs for setup details, required scopes, and configuration.
Secrets
ENABLE_GOOGLE_DRIVE_INLINE_PICKER_URL— An API key that enables theGenerateGoogleFilePickerUrltool to produce a Google Drive file-picker URL. This key gates access to the inline picker feature; without it, the tool cannot generate picker URLs. Obtain it from the Arcade dashboard secrets page or by contacting Arcade support, as this is an Arcade-managed feature flag rather than a key issued directly by Google.
For general guidance on configuring secrets in Arcade tools, see the Arcade secrets docs.
Available tools(13)
13 of 13 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Comment on a specific document by its ID.
Reaches only documents this app has been granted edit access to — by default,
those it created or the user picked.
The comment is posted as the connected account and notifies the document's
collaborators. | 1 | ||
Create an empty Google Docs document with the specified title.
The document is owned by the connected account and lands in its Drive root. Returns
the new document's id, which every other tool here takes as its target. To create a
document that already has content, use the tool that takes text rather than creating
an empty one and appending to it. | |||
Create a Google Docs document with the specified title and text content.
When input_format is MARKDOWN, the text_content is parsed as Markdown and the resulting
document is formatted with headings, bold, italic, bullet lists, and numbered lists. | |||
Read or edit a Google Docs document using structured batchUpdate requests.
Reaches only documents this app has been granted edit access to — by default,
those it created or the user picked.
When called without requests, returns the document content in DocMD format (block IDs,
character indices, and text styles). When called with requests, applies the edits and
returns the updated DocMD. Use the DocMD indices from the response to construct
requests for subsequent calls. | 1 | ||
Generate a URL where the user can grant this app access to specific Drive files.
Check `url` first. An empty `url` with a `reason` means this app already reaches every
document the connected account can open, so there is no per-file grant to request: this
tool cannot change any outcome, and a document that could not be read is one the
account itself cannot open. Do not retry it.
Otherwise the URL opens Google's first-party Drive picker, where the user selects which
files to share with this application — it is not a sign-in or credential prompt. Use
this when a prior tool reported that a file was not found or access was denied, and the
user expects the file to exist. After the user completes the picker flow, retry the
prior tool. | |||
Get the latest version of the specified Google Docs document as DocMD.
Reaches only documents this app has been granted access to — by default, those it
created or the user picked.
The DocMD output will include tags that can be used to annotate the document with location
information, the type of block, block IDs, and other metadata. If the document has tabs,
all tabs are included in sequential order unless a specific tab_id is provided. | 1 | ||
Get a Google Docs document as the raw Google Docs API document resource.
Returns the API's own structure, including every tab's content. Reaches only
documents this app has been granted access to — by default, those it created or the
user picked. Use this when the document's exact structure matters, such as reading
style runs, named ranges or inline object properties. For reading or summarizing the
text, prefer the DocMD form, which is far smaller and carries the character indices
edits are built from. | 1 | ||
Get metadata for a Google Docs document including hierarchical tab structure.
Reaches only documents this app has been granted access to — by default, those it
created or the user picked.
Returns document title, ID, URL, total character count, and nested tab information
with character counts for each tab. | 1 | ||
Appends text to the end of a Google Docs document.
Reaches only documents this app has been granted edit access to — by default,
those it created or the user picked.
Each tab keeps its own content and its own character indices, so the text lands at the
end of one tab rather than the end of the file. | 1 | ||
List comments on the specified Google Docs document.
Reaches only documents this app has been granted access to — by default, those it
created or the user picked.
Returns each comment's text, its replies, and the display name of whoever wrote it.
Drive does not document an order for comments, so do not read the first one as the
most recent; compare createdTime when recency matters. A long-running document can
carry thousands of comments, so results are paged rather than returned whole, and the
counts describe the page in hand rather than the document. | 1 | ||
Searches for documents in the user's Google Drive and returns documents with their main body
content and tab metadata. Excludes documents that are in the trash.
Searches only the documents this app has been granted access to — by default, those
it created or the user picked.
Content it returns was written by whoever has edited each document, which need not be
the connected account and need not be the owner.
Returns main body content only with metadata about tabs. Use get_document_as_docmd() to retrieve
full tab content for specific documents. Use search_documents() for metadata-only searches. | 1 | ||
Searches for documents in the user's Google Drive. Excludes documents in trash.
Searches only the documents this app has been granted access to — by default, those
it created or the user picked.
Returns metadata only. Use get_document_metadata or get_document_as_docmd for content. | 1 | ||
Get the connected Google account's profile: name, email address and profile picture.
Use this to confirm which account the connection is acting as before creating or
editing a document, or when the user asks who they are signed in as.
It reads the Google profile and opens no document, so it does not report which
documents this app can reach. To find out whether a particular document is reachable,
search for it or open it. Fields Google does not return are omitted rather than empty. |
Last updated on