---
title: "Google Docs"
description: "Read documents and tab content, create documents and apply ordered batch edits with revision preconditions through the official Google Docs API. Each command makes one explicit request. Select read commands for document"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Docs

<p>Read documents and tab content, create documents and apply ordered batch edits with revision preconditions through the official Google Docs API. Each command makes one explicit request. Select read commands for document read access; enabling writes requires new consent. Batch edits can change existing shared documents. Drive file selection, export and permission management are separate integrations.</p>

<details data-command-index><summary>What you can do (3)</summary>
<h2>What you can do</h2>
<p>Available commands: 3 (1 read, 2 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/google-docs#command-google-docs-docs-documents-batchupdate">Applies one or more updates to the document</a> — <code>google-docs.docs.documents.batchupdate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/google-docs#command-google-docs-docs-documents-create">Creates a blank document using the title given in the request</a> — <code>google-docs.docs.documents.create</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/google-docs#command-google-docs-docs-documents-get">Gets the latest version of the specified document.</a> — <code>google-docs.docs.documents.get</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/google-docs">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Google Docs, then enter the issued values in the connection form below.</p>
<ol>
<li>Create or reuse a Google Cloud project, enable the Google Docs API and configure its OAuth consent screen and web client. Register the exact callback shown by Tooluse.net. Enter the Google OAuth client ID and secret in this connection and authorize; no client secret belongs in an AI client. Reading requests documents.readonly; selecting editing commands requires fresh documents consent. A short-lived Google access token can be entered instead for manual testing. Use a document ID, respect revision preconditions and keep batch edits explicit. Create a separate scoped Tooluse.net API key for Claude Code, Codex or Cursor. Public OAuth distribution still requires Google’s applicable verification.</li>
</ol>
<p><a href="https://developers.google.com/workspace/docs/api/quickstart/js">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Google access token (optional with OAuth)</td>
<td>Optional</td>
</tr>
<tr>
<td>Google OAuth client ID</td>
<td>Optional</td>
</tr>
<tr>
<td>Google OAuth client secret</td>
<td>Optional</td>
</tr>
<tr>
<td>Registered OAuth redirect URI (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Return URL after authorization</td>
<td>Optional</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "path": {
      "documentId": "example"
    }
  }
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-google-docs-docs-documents-batchupdate">
<summary><span>Applies one or more updates to the document — <code>google-<wbr>docs.<wbr>docs.<wbr>documents.<wbr>batchupdate</code></span></summary>
<p>Run <strong>Applies one or more updates to the document</strong> with Google Docs. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/google-docs?command=google-docs.docs.documents.batchupdate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.$.xgafv</code></td>
<td>string</td>
<td>Optional</td>
<td>V1 error format.</td>
<td><code>enum: [&quot;1&quot;,&quot;2&quot;]</code></td>
</tr>
<tr>
<td><code>query.fields</code></td>
<td>string</td>
<td>Optional</td>
<td>Selector specifying which fields to include in a partial response.</td>
<td></td>
</tr>
<tr>
<td><code>query.prettyPrint</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Returns response with indentations and line breaks.</td>
<td><code>default: true</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.documentId</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the document to update.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/BatchUpdateDocumentRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/google-docs/commands/google-docs.docs.documents.batchupdate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "documentId": "example"
  },
  "body": {}
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-google-docs-docs-documents-create">
<summary><span>Creates a blank document using the title given in the request — <code>google-<wbr>docs.<wbr>docs.<wbr>documents.<wbr>create</code></span></summary>
<p>Run <strong>Creates a blank document using the title given in the request</strong> with Google Docs. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/google-docs?command=google-docs.docs.documents.create">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.$.xgafv</code></td>
<td>string</td>
<td>Optional</td>
<td>V1 error format.</td>
<td><code>enum: [&quot;1&quot;,&quot;2&quot;]</code></td>
</tr>
<tr>
<td><code>query.fields</code></td>
<td>string</td>
<td>Optional</td>
<td>Selector specifying which fields to include in a partial response.</td>
<td></td>
</tr>
<tr>
<td><code>query.prettyPrint</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Returns response with indentations and line breaks.</td>
<td><code>default: true</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/Document&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/google-docs/commands/google-docs.docs.documents.create">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {}
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-google-docs-docs-documents-get">
<summary><span>Gets the latest version of the specified document. — <code>google-<wbr>docs.<wbr>docs.<wbr>documents.<wbr>get</code></span></summary>
<p>Run <strong>Gets the latest version of the specified document.</strong> with Google Docs. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/google-docs?command=google-docs.docs.documents.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.$.xgafv</code></td>
<td>string</td>
<td>Optional</td>
<td>V1 error format.</td>
<td><code>enum: [&quot;1&quot;,&quot;2&quot;]</code></td>
</tr>
<tr>
<td><code>query.fields</code></td>
<td>string</td>
<td>Optional</td>
<td>Selector specifying which fields to include in a partial response.</td>
<td></td>
</tr>
<tr>
<td><code>query.prettyPrint</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Returns response with indentations and line breaks.</td>
<td><code>default: true</code></td>
</tr>
<tr>
<td><code>query.commentsViewMode</code></td>
<td>string</td>
<td>Optional</td>
<td>The comments view mode to apply to the document. This allows viewing the document with comments omitted or included. If one is not specified, COMMENTS_VIEW_MODE_OMITTED is used. If you set comments_view_mode to any value, you must also set include_tabs_content to <code>true</code> or use a field mask that references the Document.tabs field (or any subfield). If you set comments_view_mode to COMMENTS_VIEW_MODE_INCLUDED, you must also explicitly set suggestions_view_mode to SUGGESTIONS_INLINE. If you set comments_view_mode to COMMENTS_VIEW_MODE_INCLUDED or COMMENTS_VIEW_MODE_DEFAULT_FOR_CURRENT_ACCESS, you may not set suggestions_view_mode to PREVIEW_WITHOUT_SUGGESTIONS or PREVIEW_SUGGESTIONS_ACCEPTED.</td>
<td><code>enum: [&quot;COMMENTS_VIEW_MODE_UNSPECIFIED&quot;,&quot;COMMENTS_VIEW_MODE_DEFAULT_FOR_CURRENT_ACCESS&quot;,&quot;COMMENTS_VIEW_MODE_OMITTED&quot;,&quot;COMMENTS_VIEW_MODE_INCLUDED&quot;]</code></td>
</tr>
<tr>
<td><code>query.includeTabsContent</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Whether to populate the <code>Document.tabs</code> field instead of the text content fields like <code>body</code> and <code>documentStyle</code> on <code>Document</code>. - When <code>true</code>: Document content populates in the <code>Document.tabs</code> field instead of the text content fields in <code>Document</code>. - When <code>false</code>: The content of the document&#39;s first tab populates the content fields in <code>Document</code> excluding <code>Document.tabs</code>. If a document has only one tab, then that tab is used to populate the document content. <code>Document.tabs</code> will be empty. If you use a field mask that references the <code>Document.tabs</code> field (or any subfield), the API implicitly treats the request as if you set <code>include_tabs_content</code> to <code>true</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.suggestionsViewMode</code></td>
<td>string</td>
<td>Optional</td>
<td>The suggestions view mode to apply to the document. This allows viewing the document with all suggestions inline, accepted or rejected. If one is not specified, DEFAULT_FOR_CURRENT_ACCESS is used.</td>
<td><code>enum: [&quot;DEFAULT_FOR_CURRENT_ACCESS&quot;,&quot;SUGGESTIONS_INLINE&quot;,&quot;PREVIEW_SUGGESTIONS_ACCEPTED&quot;,&quot;PREVIEW_WITHOUT_SUGGESTIONS&quot;]</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.documentId</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the document to retrieve.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/google-docs/commands/google-docs.docs.documents.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "documentId": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developers.google.com/workspace/docs/api/reference/rest">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/google-docs/index.mdx