Google Docs MCP integration for AI agents.
Connect AI agents to Google Docs through 32 structured actions, including export document as pdf, create document, delete content range, and copy document. R…
- ACTION CONTRACTS
- 32
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Google Docs integration exposes
The Google Docs Agent App exposes 32 provider-backed actions for productivity work. Its current contract lets an authorized agent export a google docs file as a pdf through google drive, create a google docs document and optionally insert initial text at the beginning, and delete a content range from a google docs document. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Google Docs account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Google Docs capabilities.
Showing 12 of 32 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
export_document_as_pdfREADExport a Google Docs file as a PDF through Google Drive.
INPUTS: file_id / filename
create_documentWRITECreate a Google Docs document and optionally insert initial text at the beginning.
INPUTS: title / text
delete_content_rangeHIGH IMPACTDelete a content range from a Google Docs document.
INPUTS: document_id / range
copy_documentREVIEWCopy an existing Google Docs document through Google Drive.
INPUTS: document_id / title / include_shared_drives
create_document2WRITECreate a blank Google Docs document.
INPUTS: title
create_footerWRITECreate a footer in a Google Docs document.
INPUTS: document_id / type / section_break_location
create_footnoteWRITECreate a footnote in a Google Docs document.
INPUTS: documentId / location / endOfSegmentLocation
create_headerWRITECreate a header in a Google Docs document and optionally insert initial text.
INPUTS: documentId / type / text / sectionBreakLocation
create_named_rangeWRITECreate a named range over a specific span in a Google Docs document.
INPUTS: documentId / name / rangeStartIndex / rangeEndIndex / rangeSegmentId
create_paragraph_bulletsWRITEAdd bullets to paragraphs within a specified range in a Google Docs document.
INPUTS: document_id / createParagraphBullets
delete_footerHIGH IMPACTDelete a footer from a Google Docs document.
INPUTS: document_id / footer_id / tab_id
delete_headerHIGH IMPACTDelete a header from a Google Docs document.
INPUTS: document_id / header_id / tab_id
INPUT CONTRACTS
Know what the action needs before it runs.
export_document_as_pdf
file_idREQUIRED- The ID of the Google Docs file to export.
filenameOPTIONAL- The filename for the exported PDF.
create_document
titleREQUIRED- The title of the new document.
textOPTIONAL- Initial text to insert at the beginning of the document.
delete_content_range
document_idREQUIRED- The ID of the Google Docs document.
rangeREQUIRED- A JSON-like object with arbitrary string keys.
copy_document
document_idREQUIRED- The ID of the Google Docs document to copy.
titleOPTIONAL- The title for the copied document.
include_shared_drivesOPTIONAL- Whether to include shared drives when locating the source document.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Export Document As Pdf
Export a Google Docs file as a PDF through Google Drive. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
export_document_as_pdfControl Create Document
Create a Google Docs document and optionally insert initial text at the beginning. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_documentVerify with Create Document
Create a Google Docs document and optionally insert initial text at the beginning. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_documentSAFETY BOUNDARY
Operate Google Docs with explicit limits
- Authorize Google Docs with OAuth 2.0 and grant only the provider access required by the selected actions.
- 18 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_content_range`, `delete_footer`, and `delete_header` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `https://www.googleapis.com/auth/documents`, `https://www.googleapis.com/auth/drive.file`, `https://www.googleapis.com/auth/documents.readonly`, and `https://www.googleapis.com/auth/spreadsheets.readonly`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Google Docs task completed successfully.
CONNECTION MODEL
OAuth 2.0
Google Docs uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 11
- HIGH IMPACT
- 7
- REVIEW SIGNALS
- 9
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Google Docs.