Skip to main content
Glama
tszaks

Gmail Multi-Inbox MCP Server

by tszaks

sheets_delete_tab

Delete unused sheet tabs from a spreadsheet to keep data organized. Specify account, spreadsheet ID, and sheet title.

Instructions

Delete a sheet tab from a spreadsheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountYesAccount id.
sheet_titleYesName of the sheet tab to delete.
spreadsheet_idYesSpreadsheet ID.
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that deletion is destructive or irreversible, nor any permissions or side effects. The description merely repeats the verb 'delete' without adding context beyond the tool name.

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, concise sentence that is front-loaded and contains no wasted words. It is appropriately sized for a simple operation.

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 simple deletion tool with fully described parameters, the description is minimally sufficient but lacks behavioral context such as irreversibility or error conditions. It is not misleading but does not fully elaborate on the operational impact.

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?

The input schema provides 100% coverage with descriptions for all three parameters, so the description adds no additional parameter-specific meaning. The baseline of 3 is appropriate since the schema carries the burden.

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 a sheet tab from a spreadsheet' with a specific verb and resource. It distinguishes itself from sibling tools like sheets_add_tab and sheets_rename_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 usage (when you need to delete a sheet tab) but provides no explicit guidance on when to use this tool versus alternatives, nor 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.

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/tszaks/ghub'

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