Skip to main content
Glama
dipseth

google-workspace-unlimited

Modify Sheet Values

modify_sheet_values
Destructive

Modify values in a specific range of a Google Sheet: write new data, update existing cells, or clear the range. Supports raw or user-entered input.

Instructions

Modify 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 Python list [["cell1", "cell2"], ["cell3", "cell4"]] or JSON string '[["cell1", "cell2"], ["cell3", "cell4"]]'. 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. When True, 'values' parameter is ignored.
spreadsheet_idYesThe ID of the spreadsheet. Required.
user_google_emailNoThe user's Google email address for Sheets access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).
value_input_optionNoHow to interpret input values: 'RAW' (values not parsed) or 'USER_ENTERED' (values parsed as if typed by user)USER_ENTERED

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if operation failed
rangeYesRange that was modified
messageYesSuccess or error message
successYesWhether the operation succeeded
operationYesType of operation performed ('update', 'clear')
updatedRowsNoNumber of rows updated
clearedRangeNoRange that was cleared
updatedCellsNoNumber of cells updated
spreadsheetIdYesUnique identifier for the spreadsheet
updatedColumnsNoNumber of columns updated
Behavior3/5

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

Annotations already indicate destructiveHint=true; description adds no further behavioral context beyond stating modification actions. No mention of side effects, auth needs, or rate limits.

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?

One sentence, 15 words, front-loaded with verb and resource. No wasted words.

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?

Description is minimal but adequate given the schema covers parameters and output schema exists. Lacks context on operation selection (write vs clear) and prerequisites.

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 parameters are already well-documented. Description adds no new meaning beyond what's in the schema.

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?

Description clearly states verb 'modify', resource 'values in a specific range', and actions 'write, update, or clear'. Distinguishes from sibling tools like read_sheet_values and 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 Guidelines3/5

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

Implies usage for modifying sheet values but provides no explicit when-to-use or when-not-to-use guidance relative to siblings. Missing exclusions or alternatives.

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/dipseth/google_workspace_fastmcp2'

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