insert_doc_person_chip
Insert a person smart chip in Google Docs by specifying the email and position. The chip displays the person's name and contact card when the document is opened.
Instructions
Insert an @mention-style person chip at a specific position in a document.
Writes the person's email as linked text (href = mailto:<email>). When
Google Docs renders the document, that linked-email pattern is
auto-converted into a rich person chip — a small inline pill showing the
person's name, avatar, and hover card. The chip is a "smart chip" and
shows up in get_doc_smart_chips as type person.
Requires OAuth scope: https://www.googleapis.com/auth/documents (write).
For a Drive-file chip instead, use insert_doc_file_chip. For a plain
hyperlink, use insert_doc_link.
Note: The chip only renders correctly once a collaborator or the owner opens the doc in the Google Docs UI — Docs does the text-to-chip conversion client-side on render. The API always stores the raw linked email. Person resolution uses the email only; if the email doesn't match a Google account visible to the viewer, it falls back to plain linked text.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| user_google_email | Yes | ||
| document_id | Yes | Google Docs document ID (from the URL after `/document/d/`). | |
| Yes | Email address of the person to @mention, e.g., `alice@example.com`. Must be a valid email; the Docs client uses it to look up the contact card at render time. | ||
| index | No | 1-based character position in the document body where the chip is inserted. Default `1` = start of body. Use `inspect_doc_structure` to find exact indices for non-trivial placements. Ignored contextually when `tab_id` is set — index resolves within the specified tab's content. | |
| tab_id | No | Optional tab ID to target a specific tab. Get it from `list_doc_tabs`. Omit for single-body (legacy) documents. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |