mcp-google-sheets-server

sheets_create

Creates a new Google Sheets spreadsheet with optional initial data and theme (light or dark) for immediate use.

Instructions

Create a new Google Sheets with optional initial data and formatting

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": {
      "title": "<title>"
    },
    "name": "sheets_create"
  }
}

Input Schema

Name	Required	Description	Default
`theme`	No	Theme for the spreadsheet	LIGHT
`title`	Yes	The title of the spreadsheet
`initialData`	No	Optional initial data to populate

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for disclosing behavior. It does not mention what happens on creation (e.g., returns a spreadsheet ID, opens a new file), side effects, or whether the tool is read-only or mutating. The phrase 'Create a new' implies a mutation but leaves specifics unstated.

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?

The description is a single, concise sentence that efficiently conveys the core action and optional enhancements. It is well-structured but could benefit from breaking out key details about parameters or return values without sacrificing brevity.

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

Completeness2/5

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

Given the large set of sibling tools, the description lacks context on how this tool differs from closely related ones (e.g., 'sheets_create_sheet' for creating a sheet within an existing spreadsheet). It also omits any output schema or return value details, making it incomplete for an agent to fully understand the tool's place and expectations.

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?

All three parameters are described in the schema: title, theme, and initialData. However, the descriptions are minimal. 'initialData' is described only as 'Optional initial data' without specifying its structure or format, and 'theme' is an enum but its effect is not explained. The schema coverage is complete but shallow.

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?

The description clearly states the verb 'Create' and the resource 'a new Google Sheets', but it does not specify whether this creates a spreadsheet or a sheet within a spreadsheet, which is ambiguous given the sibling tool 'sheets_create_sheet'. The mention of 'optional initial data and formatting' adds clarity but could be more precise.

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?

No guidance is provided regarding when to use this tool versus alternatives like 'sheets_create_sheet' or 'sheets_create_chart'. There is no mention of prerequisites, scenarios, or limitations, leaving the agent to infer appropriate usage from the tool name alone.

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