Skip to main content
Glama
Sign In
Gmail Multi-Inbox MCP Server

Gmail Multi-Inbox MCP Server

by tszaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sheets_write

Write values to a Google Sheets range, overwriting existing data. Specify spreadsheet ID, range, and a 2D array of values for precise updates.

Instructions

Write values to a Google Sheet range. Overwrites existing values in the specified range.

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": {
      "account": "<account>",
      "spreadsheet_id": "<spreadsheet_id>",
      "range": "<range>",
      "values": "<values>"
    },
    "name": "sheets_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesA1 notation range, e.g. "Sheet1!A1".
valuesYes2D array of values to write (rows × columns).
accountYesAccount id.
spreadsheet_idYesSpreadsheet ID.
value_input_optionNoHow values are parsed (default USER_ENTERED).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the key destructive behavior ('Overwrites existing values'), which is important. However, it does not mention whether the operation is reversible, whether it affects only the specified range, or if authentication is required. It adds some value but lacks depth.

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 two sentences, front-loaded with the action and resource, and every word earns its place. There is no redundancy or filler.

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 write operation with fully documented schema, the description plus schema covers the essential use case: writing and overwriting a range. It does not explain return values (no output schema), but that is not critical for a write tool. The lack of explicit mention of optional value_input_option behavior is compensated by the schema enum description.

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 each parameter is already documented with descriptions. The tool description does not add meaningful detail beyond the schema, aside from emphasizing the overwrite behavior. Baseline 3 is appropriate since the schema handles parameter semantics well.

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 clearly states the action with a specific verb and resource: 'Write values to a Google Sheet range.' It also adds the crucial differentiator 'Overwrites existing values in the specified range,' which distinguishes it from sibling tools like sheets_append.

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 description implies when to use the tool ('when you need to overwrite values') but does not explicitly mention alternatives or exclusion criteria. It does not name sheets_append or provide 'when not to use' guidance, though the overwrite mention offers some context.

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