Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_create

Create a Google Sheet with optional tab names and initial data so you can start structured spreadsheets from scratch.

Instructions

Create a Google Sheet with optional tab names and initial data for the first tab.

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

NameRequiredDescriptionDefault
dataNoRows for the first tab; first row is typically headers
tabsNo
titleYes
folderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered structurally. The description adds nothing further: it does not say where the new sheet lands (My Drive root vs. folderId), whether the returned spreadsheet is shared or private, or what identifier comes back. With no output schema, that last point is a real gap for a tool whose main output is an ID.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the compression is partly why the folderId and return-value details are absent.

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?

For a 4-parameter creation tool with no output schema and three undocumented parameters, the description leaves an agent unable to predict placement, return value, or the meaning of half the inputs. It states the core action but not enough to invoke the tool confidently the first time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% — only `data` is documented in the schema. The description partially compensates by explaining `tabs` and `data` (rows for the first tab), but `folderId` and `title` get no semantic treatment at all, and folderId is the parameter that most affects behavior.

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?

Names a specific verb and resource ('Create a Google Sheet') and scopes what the optional inputs do ('tab names and initial data for the first tab'). It is clearly distinct from sheets_write / sheets_append_rows, but it never names or contrasts those siblings explicitly.

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 word 'Create' implies this is for new spreadsheets rather than existing ones, which is the key routing decision against sheets_write. There is no explicit when-to-use, when-not-to-use, or prerequisite statement (e.g. required scopes or Drive permissions).

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