Google Sheets and Drive MCP

Overview Schema Source Related Servers Discussions Admin

copy_range

Copy values, formulas, formatting, or conditional rules from one range to another in a Google Sheet. Specify source range, target start cell, and paste type.

Instructions

Copy values, formulas, formatting, or rules within one spreadsheet.

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>",
      "source_range": "<source_range>",
      "target_start_cell": "<target_start_cell>"
    },
    "name": "copy_range"
  }
}

Input Schema

Name	Required	Default
`paste_type`	No	PASTE_VALUES
`orientation`	No	NORMAL
`source_range`	Yes
`spreadsheet_id`	Yes
`target_start_cell`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so description carries full burden. It only states basic copy behavior, omitting details like target overwrite, reversibility, or permissions. Insufficient for a mutation tool.

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?

Single sentence with no redundancy. Front-loads action and scope. Every word earns its place.

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

Completeness2/5

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

Tool has 5 parameters and a meaningful operation, yet description is minimal. No explanation of output (though output schema exists), range formats, or paste behavior. Incomplete given complexity.

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

Parameters1/5

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

Schema has 0% description coverage for 5 parameters. Description does not explain any parameter (e.g., source_range format, paste_type enum, orientation). Relies entirely on schema, which lacks descriptions.

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 verb (Copy) and the resource (within one spreadsheet), listing specific items (values, formulas, formatting, or rules). It distinguishes from siblings like copy_sheet or write_range.

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 tool versus alternatives (e.g., copy_sheet). Does not mention constraints like same-spreadsheet-only or when to prefer other tools.

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