Skip to main content
Glama
taylorwilsdon

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Insert Smart Chips

insert_smart_chips
DestructiveIdempotent

Insert Google Workspace Smart Chips (Drive files, folders, or people) into any Google Sheets cell or range. Specify URLs or emails to enrich your spreadsheet with clickable references.

Instructions

Inserts Google Workspace Smart Chips (Drive files/folders or People) into a Google Sheet cell or range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chipsYesSmart chip(s) to insert: - A single URL or email string for a single cell (e.g., "https://drive.google.com/drive/folders/123", "user@example.com"). - A list of URLs or emails for a single cell (multiple chips) or across cells (e.g., ["https://...", "https://..."]). - A 2D list of URLs/emails matching a grid range. For a single-row or single-column range, each inner list is instead the chips for one cell (e.g., [["a@x.com", "b@x.com"]] puts both chips in the first cell of "A1:C1"). - A dict or list of dicts with explicit properties (e.g., {"type": "drive", "uri": "..."}, {"type": "person", "email": "..."}). - A JSON-encoded string representing any of the above formats.
chip_typeNoExplicit chip type if passing raw strings: "drive" (default for URLs/IDs) or "person" (default for emails).
range_nameYesTarget cell or range (e.g., "Sheet1!F3", "Sheet1!F3:F23", "F3"). Required.
spreadsheet_idYesThe ID of the spreadsheet. Required.
user_google_emailYesThe user's Google email address. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.28.0

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating operation. However, the description adds no context about side effects (e.g., whether inserting chips overwrites existing cell content, or whether it appends to the existing value). With a destructive mutation, the description should at least hint at overwrite behavior; it does not.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler. It states the action, the resource, and the target in a compact way that an agent can parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema (100% coverage) and the presence of an output schema, the description is sufficient for an agent to understand the tool's core purpose. It lacks usage guidance and behavioral nuance, but those are captured in other dimensions; overall, it is complete enough for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers all 5 parameters with detailed descriptions, including the flexible 'chips' format and the 'chip_type' default. The tool description itself adds no extra meaning beyond the schema. Since schema coverage is 100%, a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Inserts'), a distinct resource ('Google Workspace Smart Chips (Drive files/folders or People)'), and the target ('Google Sheet cell or range'). This clearly distinguishes it from sibling tools like modify_sheet_values or format_sheet_range, which operate on plain values or formatting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., modify_sheet_values for plain values, or read_sheet_values for reading). The description does not mention any exclusions, prerequisites, or conditions that would steer an agent toward or away from this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools