Skip to main content
Glama
Sign In
MCP Google Sheets

MCP Google Sheets

by toantran201
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Add Columns

add_columns

Insert empty columns into a Google Sheet at a specified position or append them to the right edge.

Instructions

Inserts empty columns into a sheet tab at a position, or appends them at the right edge.

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>",
      "sheet_name": "<sheet_name>",
      "count": "<count>"
    },
    "name": "add_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of empty columns to insert
sheet_nameYesTarget sheet tab name
spreadsheetYesTarget spreadsheet: a full Google Sheets URL (https://docs.google.com/spreadsheets/d/<ID>/edit...) or a bare spreadsheet ID
start_columnNo1-based column index to insert BEFORE (e.g. 3 inserts before column C). Omit to append at the right edge of the sheet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description should disclose side effects. It states the basic behavior (insert or append empty columns) but does not mention that inserting shifts existing columns to the right or any other impacts. The description is not misleading but lacks detail on data integrity or constraints.

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 a single, front-loaded sentence that directly states the action and the two scenarios. Every word is necessary and there is no fluff. It is optimally concise for its complexity.

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?

Given the tool's complexity (mutation, 4 parameters, no output schema, no annotations), the description adequately covers the core functionality of inserting or appending columns. It lacks details on error conditions or return values, but the schema covers parameter details. It is slightly above average in completeness.

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 the baseline is 3. The description adds no extra meaning beyond the schema; it only repeats the insert/append concept. The schema already documents each parameter, including the optional start_column behavior.

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 verb 'Inserts' and the resource 'empty columns into a sheet tab', and distinguishes between two modes: inserting at a specific position or appending at the right edge. This differentiates it from sibling tools like add_rows (which adds rows) and create_sheet (creates a whole sheet).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/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 add empty columns to a sheet) and distinguishes the two insertion modes. However, it does not explicitly exclude alternatives or provide guidance on when not to use it. The purpose is clear enough for an agent to select it over siblings.

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