Skip to main content
Glama

delete_sheet

Removes a sheet or tab from a spreadsheet using its name or numeric sheet ID.

Instructions

Delete a sheet/tab by name or numeric sheetId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetYes
spreadsheet_idYes
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It states 'Delete' but does not disclose that the operation is irreversible, what happens to data, whether it is synchronous, or any required authentication. A destructive tool should explicitly warn about permanence.

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?

A single, well-structured sentence that front-loads the key action and resource. No unnecessary words; every part earns its place.

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?

Given the simple operation and no output schema, the description covers the basics but lacks critical details like irreversibility warning and return value. For a deletion tool, more context is expected.

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 0%, so the description must compensate. It clarifies that 'sheet' can be a name or numeric ID, which adds meaning beyond the bare schema. However, the 'spreadsheet_id' parameter is not explained, and no format details are provided for either parameter.

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 'sheet/tab', and specifies the identifiers ('name or numeric sheetId'). This distinguishes it from siblings like add_sheet, rename_sheet, and other deletion tools (delete_table, delete_chart, etc.).

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., clear_range to empty a sheet without deleting it). No mention of when not to use it or prerequisites like required permissions.

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/richmcpharlin/google-sheets-mcp'

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