Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Modify Sheet Values

modify_sheet_values
Destructive

Write, update, or clear values in a specified Google Sheets range using spreadsheet ID and range name, with configurable input options.

Instructions

Modifies values in a specific range of a Google Sheet - can write, update, or clear values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valuesNo2D array of values to write/update. Can be a JSON string or Python list. Required unless clear_values=True.
range_nameYesThe range to modify (e.g., "Sheet1!A1:D10", "A1:D10"). Required.
clear_valuesNoIf True, clears the range instead of writing values. Defaults to False.
spreadsheet_idYesThe ID of the spreadsheet. Required.
user_google_emailYesThe user's Google email address. Required.
value_input_optionNoHow to interpret input values ("RAW" or "USER_ENTERED"). Defaults to "USER_ENTERED".USER_ENTERED

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed18 schema fields changedv1.0.1
    • 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
+}
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. The description adds no behavioral context beyond restating the tool's purpose (write/update/clear). It does not mention that writes overwrite existing data or that clear operations are permanent, which would be valuable given the destructive hint.

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 that efficiently conveys the core action and supported operations. There is no waste or redundancy.

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?

The tool is relatively simple with 6 parameters, 3 required, and an output schema present. The description covers the basic function but lacks additional context such as side effects or typical use cases. Given the annotations and schema coverage, it meets the minimum viable completeness but does not go beyond it.

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 has 100% description coverage for all parameters, including values, clear_values, and value_input_option. The description's phrase 'can write, update, or clear values' aligns with the schema but adds no new semantic information beyond it.

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 ('Modifies') and resource ('values in a specific range of a Google Sheet'), and further clarifies the supported actions (write, update, clear). This clearly distinguishes it from sibling tools like read_sheet_values 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 provides no explicit guidance on when to use this tool versus alternatives such as append_table_rows or format_sheet_range. It does not mention exclusions or conditions that would help an agent decide between this and similar sheet-related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorwilsdon/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server