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

Gmail Multi-Inbox MCP Server

by tszaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sheets_delete_dimension

Remove rows or columns from a Google Sheets spreadsheet by supplying the sheet, dimension (ROWS or COLUMNS), start index, and count.

Instructions

Delete rows or columns from a sheet.

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>",
      "sheet_title": "<sheet_title>",
      "dimension": "<dimension>",
      "start_index": "<start_index>",
      "count": "<count>"
    },
    "name": "sheets_delete_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of rows or columns to delete.
accountYesAccount id.
dimensionYesWhether to delete rows or columns.
sheet_titleYesSheet tab name.
start_indexYesZero-based index of the first row/column to delete.
spreadsheet_idYesSpreadsheet ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.2

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. While 'Delete' implies a destructive operation, it does not disclose that deletion is likely permanent, that it shifts indices of remaining rows/columns, or any other side effects. This is a significant gap for a mutation tool.

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, direct sentence that wastes no words. It is appropriately front-loaded with the action and target resource.

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 destructive tool with no annotations and no output schema, the description is too sparse. It fails to mention irreversible consequences, how indices are affected, or any operational context. The schema provides parameter details but not higher-level behavioral context.

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%, with all parameters already documented (e.g., start_index as zero-based, dimension as ROWS/COLUMNS). The tool description adds no additional parameter semantics, so a baseline score of 3 is appropriate.

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 ('Delete') and the resource ('rows or columns from a sheet'), and the tool name reinforces this. It distinguishes from sibling tools like sheets_insert_dimension and sheets_delete_tab.

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 (whenever rows or columns need to be removed from a sheet), but it does not provide explicit guidance on when to prefer this over alternatives, nor does it mention any exclusions or prerequisites.

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