Google Sheets and Drive MCP

Overview Schema Source Related Servers Discussions Admin

create_pivot_table

Create a Google Sheets pivot table from a source range, specifying row and value columns, optional column grouping, and summary function.

Instructions

Create a native Google Sheets pivot table from a bounded source range.

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_cell": "<target_cell>",
      "row_columns": "<row_columns>",
      "value_columns": "<value_columns>"
    },
    "name": "create_pivot_table"
  }
}

Input Schema

Name	Required	Default
`row_columns`	Yes
`show_totals`	No
`target_cell`	Yes
`source_range`	Yes
`value_columns`	Yes
`column_columns`	No
`spreadsheet_id`	Yes
`summarize_function`	No	SUM

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 28, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only says 'create a pivot table' without detailing side effects, permissions needed, or error handling for invalid ranges.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks necessary detail. It could be restructured to include key parameter info while remaining succinct.

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

Completeness1/5

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

For a tool with 8 parameters, 5 required, and a complex operation, the description is severely incomplete. It does not address parameter arrays, default values, or return value (despite having an output schema).

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 parameter descriptions have 0% coverage, and the tool description does not explain any parameters (e.g., row_columns, value_columns, summarize_function). The agent has no understanding of what each parameter means.

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 uses a specific verb 'Create' and identifies the resource as 'native Google Sheets pivot table', with a constraint 'from a bounded source range'. This clearly differentiates it from sibling tools like read_range or create_chart.

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. Lacks context such as prerequisites (e.g., data must be contiguous) or when not to use (e.g., if data is not tabular).

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