Skip to main content
Glama
GhazwaPasha

Google Workspace MCP Server

by GhazwaPasha

sheets_delete_dimension

Delete rows or columns from a Google Sheet by supplying the dimension (ROWS/COLUMNS) and start/end indices; remaining content shifts automatically.

Instructions

Delete rows or columns, shifting remaining content. dimension: 'ROWS' or 'COLUMNS'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
dimensionYes
end_indexYes
start_indexYes
spreadsheet_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the behavioral transparency burden. It usefully discloses that remaining content shifts after deletion, which is a behavioral trait beyond the schema. However, it does not mention irreversible destruction, permission requirements, or other side effects, leaving gaps 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 two short sentences, front-loaded with the primary action. The second sentence efficiently enumerates the dimension values, and there is no wasted verbiage.

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

Completeness3/5

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

For a straightforward delete tool, the description covers the core operation and the dimension enum, but lacks detail on the index range semantics. The presence of an output schema offloads return-value documentation, but overall the description leaves some contextual gaps.

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?

The description adds meaning only for the 'dimension' parameter by specifying its allowed values ('ROWS' or 'COLUMNS'). It does not explain 'start_index' and 'end_index' beyond their schema titles, and with 0% schema description coverage, this is insufficient to fully understand the parameter semantics.

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'), the resource ('rows or columns'), and the side effect ('shifting remaining content'). This distinguishes it from sibling tools like sheets_delete_sheet (entire sheet) and sheets_insert_dimension (insert).

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 tool's purpose implies when to use it (when needing to remove rows or columns), but it does not explicitly compare to alternatives or state when not to use it. No exclusions or prerequisites are mentioned, so guidance is limited to the implied context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GhazwaPasha/Google-wrk-spc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server