Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

sheets_values_update

DestructiveIdempotent

Writes values to a specified spreadsheet range, replacing existing data; use when you need to update cells but accept that prior values are overwritten.

Instructions

Write values to a spreadsheet range. Overwrites the values already in the range; the previous values are not kept, so this tool is marked destructive.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "spreadsheetId": "<spreadsheetId>",
      "range": "<range>",
      "valueInputOption": "<valueInputOption>",
      "values": "<values>"
    },
    "name": "sheets_values_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesA1 notation range to write
valuesYes2D array of values as JSON string (e.g. '[["A","B"],["C","D"]]')
spreadsheetIdYesThe spreadsheet ID
valueInputOptionYesRAW or USER_ENTERED

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is structured data. The description restates the destructive consequence ('previous values are not kept'), which adds some concrete meaning but largely duplicates the destructiveHint annotation; idempotency and open-world behavior go unaddressed, and there is no note on permissions or write scope.

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?

Two short sentences, front-loaded with purpose then consequence; every clause carries information and nothing is redundant padding.

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?

For a four-parameter write tool with a fully described schema and no output schema, the description covers purpose and the key data-loss consequence, which is what an agent most needs before invoking. It stops short of explaining how valueInputOption affects parsing or whether the range must already exist, minor gaps given full schema coverage.

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 every parameter is documented in the schema with its type and, for valueInputOption, its allowed values. The description adds no parameter meaning beyond that, so the baseline of 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?

A specific verb+resource is given ('Write values to a spreadsheet range'), and the word 'overwrites' implicitly distinguishes the tool from sibling sheets_values_append. However, no sibling is named explicitly, so the differentiation is left for the agent to infer.

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

Usage Guidelines3/5

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

The overwrite/destructive framing implies when to pick this over an append-style tool, but there is no explicit 'use this instead of X' guidance, no prerequisites, and no warning about when not to use it. Usage is implied rather than stated.

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