Google Sheets Advanced MCP Server

Overview Schema Source Related Servers Discussions Admin

sheets_create_chart

Idempotent

Create bar, line, pie, or other charts in Google Sheets from a specified data range and sheet, with options for title, legend, and placement.

Instructions

Creates a chart in a Google Sheets 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>",
      "sheet_name": "<sheet_name>",
      "data_range": "<data_range>",
      "chart_type": "<chart_type>"
    },
    "name": "sheets_create_chart"
  }
}

Input Schema

Name	Required	Description
`title`	No	The title of the chart
`options`	No	Additional chart options
`position`	No	Where to place the chart
`chart_type`	Yes	The type of chart to create
`data_range`	Yes	The data range in A1 notation (e.g. A1:C20)
`sheet_name`	Yes	The name of the sheet containing the data
`spreadsheet_id`	Yes	The ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is mostly covered. The description adds nothing behavioral beyond the word 'Creates' — not where the chart is placed by default, not what happens if the range is invalid, and not what identifier is returned for later update/delete calls.

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?

It is a single front-loaded sentence with no wasted words, which is structurally sound. But the extreme brevity for a 7-parameter creation tool means it is under-specified rather than genuinely concise.

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?

This is a mutation tool with 7 parameters, nested objects, and no output schema, yet the description says nothing about the return value (e.g. a chart ID needed for the sibling update/delete tools) or default placement behavior. For a creation tool of this complexity, one sentence is not complete enough.

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?

Schema description coverage is 100% with all 7 parameters (including nested options, position, and the chart_type enum) documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Creates a chart'), so an agent immediately knows the action and object. However, it does not distinguish this from siblings like sheets_update_chart, sheets_delete_chart, or sheets_list_charts, which is the difference between a 4 and a 5.

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?

There is no guidance on when to create a chart versus updating or deleting one, no prerequisites (e.g. data must exist, a data_range must be supplied), and no mention of the alternatives available in the toolset. The agent must infer usage entirely from the name.

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