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

Modify Sheet Values

modify_sheet_values

Destructive

Writes, updates, or clears values in a specified Google Sheets range, and can insert Drive or People smart chips. Use it to edit spreadsheet cells by range and spreadsheet ID.

Instructions

Modifies values in a specific range of a Google Sheet - can write, update, or clear values, or insert Smart Chips (Drive files/folders or People).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chips`	No	Smart chip(s) to insert instead of values: - 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.
`values`	No	2D array of values to write/update. Can be a JSON string or Python list. Required unless clear_values=True or chips is provided.
`chip_type`	No	Explicit chip type if passing raw strings in chips: "drive" (default for URLs/IDs) or "person" (default for emails).
`range_name`	Yes	The range to modify (e.g., "Sheet1!A1:D10", "A1:D10"). Required.
`clear_values`	No	If True, clears the range instead of writing values. Defaults to False.
`spreadsheet_id`	Yes	The ID of the spreadsheet. Required.
`user_google_email`	Yes	The user's Google email address. Required.
`value_input_option`	No	How to interpret input values ("RAW" or "USER_ENTERED"). Defaults to "USER_ENTERED".	USER_ENTERED

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.30.1Oct 3, 2026

addedInput schema / properties / chip_type

Added value: +{
+  "default": null,
+  "description": "Explicit chip type if passing raw strings in chips: \"drive\" (default for URLs/IDs) or \"person\" (default for emails).",
+  "type": "string"
+}

addedInput schema / properties / chips

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "items": {},
+      "type": "array"
+    }
+  ],
+  "default": null,
+  "description": "Smart chip(s) to insert instead of values:\n- A single URL or email string for a single cell (e.g., \"https://drive.google.com/drive/folders/123\", \"user@example.com\").\n- A list of URLs or emails for a single cell (multiple chips) or across cells (e.g., [\"https://...\", \"https://...\"]).\n- A 2D list of URLs/emails matching a grid range. For a single-row or single-column\n  range, each inner list is instead the chips for one cell (e.g., [[\"a@x.com\", \"b@x.com\"]]\n  puts both chips in the first cell of \"A1:C1\").\n- A dict or list of dicts with explicit properties (e.g., {\"type\": \"drive\", \"uri\": \"...\"}, {\"type\": \"person\", \"email\": \"...\"}).\n- A JSON-encoded string representing any of the above formats."
+}

changedInput schema / properties / values / description

Previous value: -"2D array of values to write/update. Can be a JSON string or Python list. Required unless clear_values=True."New value: +"2D array of values to write/update. Can be a JSON string or Python list. Required unless clear_values=True or chips is provided."

Changed1 schema field changedv1.28.0Sep 24, 2026

changedInput schema / properties / values / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "type": "array"
+  }
+]

Changed18 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / clear_values / description

Added value: +"If True, clears the range instead of writing values. Defaults to False."

removedInput schema / properties / clear_values / title
```
Removed value: -"Clear Values"
```

addedInput schema / properties / range_name / description

Added value: +"The range to modify (e.g., \"Sheet1!A1:D10\", \"A1:D10\"). Required."

removedInput schema / properties / range_name / title
```
Removed value: -"Range Name"
```

removedInput schema / properties / service

Removed value: -{
-  "title": "service",
-  "type": "string"
-}

addedInput schema / properties / spreadsheet_id / description
```
Added value: +"The ID of the spreadsheet. Required."
```
removedInput schema / properties / spreadsheet_id / title
```
Removed value: -"Spreadsheet Id"
```
addedInput schema / properties / user_google_email / description
```
Added value: +"The user's Google email address. Required."
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

addedInput schema / properties / value_input_option / description

Added value: +"How to interpret input values (\"RAW\" or \"USER_ENTERED\"). Defaults to \"USER_ENTERED\"."

removedInput schema / properties / value_input_option / title
```
Removed value: -"Value Input Option"
```

changedInput schema / properties / values / anyOf

Previous value: -[
-  {
-    "items": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / values / description

Added value: +"2D array of values to write/update. Can be a JSON string or Python list. Required unless clear_values=True."

removedInput schema / properties / values / title
```
Removed value: -"Values"
```

changedInput schema / required

Previous value: -[
-  "service",
-  "user_google_email",
-  "spreadsheet_id",
-  "range_name"
-]New value: +[
+  "user_google_email",
+  "spreadsheet_id",
+  "range_name"
+]

removedInput schema / title

Removed value: -"modify_sheet_valuesArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.0Jun 10, 2025

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, covering the safety profile. The description usefully adds that the tool can clear values or insert Smart Chips, but does not state that writes overwrite existing range content, what permissions are required, or how value_input_option affects results. Adds modest context on top of annotations.

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

Conciseness4/5

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

A single front-loaded sentence covering the operation set; appropriately sized with no filler. The comma/em-dash chain is slightly run-on but every clause carries meaning.

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

Completeness3/5

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

An output schema exists and the input schema is fully documented, so return and parameter details are covered elsewhere. What is missing is the mutation context an agent needs — when to choose this over append_table_rows and what happens to existing values — leaving the definition minimally adequate for an 8-parameter destructive write tool.

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?

Schema description coverage is 100%, so the schema already documents all 8 parameters, including chips format examples and value_input_option. The description adds nothing about parameters beyond what is in the schema, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb (modifies) and resource (values in a range of a Google Sheet) and enumerates the supported operations (write, update, clear, insert Smart Chips). It distinguishes itself implicitly from read-only siblings like read_sheet_values, but never explicitly names which sibling to prefer over append_table_rows or format_sheet_range.

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?

The description says what the tool can do but gives no when-to-use guidance, no prerequisites, and no alternatives (e.g. append_table_rows for adding rows, format_sheet_range for styling). The agent must infer selection from the capability list alone.

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

Deploy Server