mcp-google-sheets

move_sheet

Destructive

Move a sheet to a specified position index to reorder tabs in a spreadsheet.

Instructions

Move a sheet/tab to a different position (reorder tabs).

Args: spreadsheet_id: The ID of the spreadsheet sheet: Name of the sheet to move index: New 0-based position index

Returns: Result of the move operation

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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "sheet": "<sheet>",
      "index": "<index>"
    },
    "name": "move_sheet"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes
`sheet`	Yes
`index`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 21, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations include destructiveHint=true but description only says 'move' and 'reorder', which is not necessarily destructive. Does not elaborate on side effects, permissions, or behavior beyond the basic operation.

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?

Very concise: one-line purpose, Args section with clear explanations, Returns section. No unnecessary text.

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?

Covers purpose and parameters, but return value is vague ('Result of the move operation'). No mention of what the result object contains, even though an output schema exists. Could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Each parameter is explained with a brief description (spreadsheet ID, sheet name, 0-based index), adding value over the schema which only has titles. No examples or constraints, but sufficient.

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?

Clearly states the tool moves a sheet/tab to reorder tabs, with specific verb and resource. Distinguishes from siblings like copy_sheet or rename_sheet.

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?

No guidance on when to use this vs alternatives. Does not specify context or restrictions (e.g., when reordering is needed versus other operations).

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