mcp-google-sheets-server

sheets_show_sheet

Reveals a hidden sheet in a Google Sheets spreadsheet to make it visible again.

Instructions

Show a hidden sheet (make it visible again)

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": {
      "spreadsheetId": "<spreadsheetId>",
      "sheetId": "<sheetId>"
    },
    "name": "sheets_show_sheet"
  }
}

Input Schema

Name	Required	Description	Default
`sheetId`	Yes	The ID of the sheet to show
`spreadsheetId`	Yes	The ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden. It indicates a state change (making visible) but does not mention idempotency, potential errors, or side effects.

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 concise sentence with no redundant information.

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

Completeness4/5

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

The description covers the core functionality. It does not address error cases or prerequisites, but for a simple unhide operation, this is acceptable. It could be more complete with a note about the sheet needing to be hidden.

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 schema already describes both parameters with full coverage. The tool description does not add any additional meaning beyond what the schema provides, so the baseline score applies.

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 (show) and the resource (hidden sheet), and the parenthetical 'make it visible again' reinforces its purpose. It distinguishes itself from the sibling 'hide_sheet' by being the inverse operation.

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 does not explicitly state when to use this tool versus alternatives, such as when you need to unhide a sheet. It only describes the action without guidance on selection criteria.

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