Docs
Docs has 3 operations in gum's generated catalog. Start with search when you know the task, use describe to inspect request fields and scopes, then dispatch through the command that matches the operation risk class.
| Count | Value |
|---|---|
| Family | Workspace documents |
| Operations | 3 |
| Risk classes | 1 read, 2 write |
| Auth strategies | 3 byo_oauth |
Start here
gum search "docs documents"
gum describe docs.documents.get
gum read docs.documents.get --args '{"documentId":"<documentId>"}' --output jsonFor write-class operations, gum requires the write command and an explicit write gate:
gum describe docs.documents.batchUpdate
gum write docs.documents.batchUpdate --allow-write --args '{"documentId":"<documentId>","requests":[]}'Operations
| Operation | Risk | Auth | Summary |
|---|---|---|---|
docs.documents.batchUpdate |
write |
byo_oauth |
Apply a batch of edit requests to a Google Doc (insert/replace text, formatting, tables, images). The core Docs editing op. |
docs.documents.create |
write |
byo_oauth |
Create a Google Doc. Request body lives in args.document. Backs the docs_create convenience tool. |
docs.documents.get |
read |
byo_oauth |
Fetch a Google Doc by document ID. Backs the docs_get convenience tool. |
Next
- Use API workflows for search, describe, invoke, and error handling.
- Use Auth guides for service-specific Google setup.
- Use Command index for CLI flags and generated help.
