| name | google-drive-comments |
| description | Create, reply to, resolve, and review Google Drive comments on Docs, Sheets, Slides, and other Drive files through Mail Pounder. Use when Codex must leave evidence-grounded comments, respond to comment threads, or resolve comments across linked Google accounts. |
Google Drive Comments
Use google_drive_get_document_comments, google_drive_get_spreadsheet_comments, google_drive_get_presentation_comments, or google_drive_get_file_comments to read live threads. Use google_drive_bulk_update_file_comments for creates, replies, and resolutions.
Workflow
- Ground the exact file and determine whether it is a Doc, Sheet, deck, or generic Drive file.
- Read the content around every intended target. Never infer location from a search snippet.
- Draft the complete batch before writing.
- Give every new top-level comment durable location evidence:
- Docs: exact
quoted_text, also quoted or named in the comment body.
- Sheets: exact
sheet_cell_range, also named in the body.
- Slides: exact
slide_number, also named in the body; include visible text when useful.
- Generic files: name the relevant page, timestamp, section, or file-level concern.
- Reject vague comments such as “this sentence” or “this slide” without matching evidence.
- Verify and report how many comments were created, replied to, or resolved.
API-created Drive comments can appear unanchored in Google editors. The written evidence is therefore part of the comment, not optional decoration.
