Skip to main content
Glama
Sign In
MCP Google Sheets

MCP Google Sheets

by toantran201
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Sheet

create_sheet

Add a new sheet tab to an existing Google Spreadsheet by providing the spreadsheet ID or URL and a title for the new tab.

Instructions

Creates a new sheet tab in the spreadsheet.

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

Input Schema

NameRequiredDescriptionDefault
titleYesName for the new sheet tab
spreadsheetYesTarget spreadsheet: a full Google Sheets URL (https://docs.google.com/spreadsheets/d/<ID>/edit...) or a bare spreadsheet ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries full burden. It only restates the action without disclosing behavioral traits such as whether it overwrites existing sheets, permissions required, or side effects. This is minimal disclosure.

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, efficient sentence that front-loads the core action. It is appropriately sized for a simple tool, though it could be more informative 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 lack of annotations and output schema, the description is incomplete. It fails to cover usage guidance, behavioral traits, or expected outcomes, which are essential for a mutation tool with no other documentation.

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 coverage is 100%, so the baseline is 3. The description adds no extra meaning to parameters beyond what the schema provides (title, spreadsheet). It is acceptable but does not enhance understanding.

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 uses a specific verb ('creates') and resource ('new sheet tab'), clearly stating the tool's function. It distinguishes from siblings like rename_sheet or add_rows by specifying 'new sheet tab', making its purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., when to create a sheet vs. how to select one). No context or prerequisites are mentioned, leaving the agent without decision criteria.

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