rename_sheet
Rename a sheet tab within a Google Spreadsheet by specifying its current name and new title.
Instructions
Rename a sheet/tab.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sheet | Yes | ||
| new_title | Yes | ||
| spreadsheet_id | Yes |
Rename a sheet tab within a Google Spreadsheet by specifying its current name and new title.
Rename a sheet/tab.
| Name | Required | Description | Default |
|---|---|---|---|
| sheet | Yes | ||
| new_title | Yes | ||
| spreadsheet_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only states 'Rename a sheet/tab.' It fails to disclose whether renaming is idempotent, any side effects on data or formulas, or required permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, highly concise, but at the expense of essential information. It is front-loaded but lacks substance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 3 required parameters, no output schema, and no annotations, the description is severely incomplete. It provides no guidance on usage, parameter semantics, or expected behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description does not mention any parameters. The agent gets no clarification on what 'sheet' (name/ID?), 'new_title', or 'spreadsheet_id' mean beyond the schema property titles.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Rename a sheet/tab' uses a specific verb (rename) and resource (sheet/tab), clearly distinguishing it from sibling tools like add_sheet, delete_sheet, and duplicate_sheet.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, such as when renaming via batch_update_advanced or using other sheet operations. The description lacks any context about prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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