Skip to main content
Glama
dudegladiator

Google Sheets MCP Server

create_chart

Create embedded charts in Google Sheets with multi-series support. Select bar, column, line, pie, area, or scatter types to visualize spreadsheet data.

Instructions

Create an embedded chart with MULTIPLE SERIES support.

Examples: - Multi-series line chart (auto-detect all columns B-F as series): create_chart("abc", 0, "LINE", "Sheet1!A1:F10", "Stock Prices")

- Explicit series columns (B=1, C=2, D=3, E=4 as separate lines):
  create_chart("abc", 0, "LINE", "A1:E10", "Comparison", 0, 7, 0, "1,2,3,4")
  
- Pie chart (single series from column B):
  create_chart("abc", 0, "PIE", "A1:B5", "Distribution")

Chart Types: - BAR: Horizontal bars (multiple series = grouped bars) - COLUMN: Vertical bars (multiple series = grouped columns) - LINE: Line graph (multiple series = multiple lines, great for trends) - PIE: Circular chart (single series only) - AREA: Stacked area chart - SCATTER: X-Y scatter plot

Multi-Series Example: Data: | Date | ONGC | BPCL | IOCL | NTPC | CIL | Range: "Sheet1!A1:F30" domain_column: 0 (Date column as X-axis) series_columns: "1,2,3,4,5" (or leave empty to auto-detect) Result: 5 lines on one chart, each representing a company

Args: spreadsheet_id: The ID from the spreadsheet URL. sheet_id: Numeric sheet ID where chart will be placed. chart_type: BAR, LINE, PIE, AREA, COLUMN, or SCATTER. data_range: A1 notation of data range (e.g., "Sheet1!A1:F30"). title: Chart title displayed at top. position_row: Row offset for chart placement (0-based). position_col: Column offset for chart placement (0=A, 5=F, 7=H). domain_column: Column index for X-axis labels (0=first column of range). series_columns: Comma-separated indices for series data (e.g., "1,2,3,4,5"). Empty = auto-detect all columns after domain_column.

Returns: JSON with chart_id for later reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
sheet_idYes
chart_typeYes
data_rangeNo
position_colNo
position_rowNo
domain_columnNo
series_columnsNo
spreadsheet_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the transparency burden. It explains behavior like series auto-detection, PIE being single-series only, and that it returns a chart_id. While it doesn't discuss permissions or reversibility, these are less critical for a creation tool.

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

Conciseness4/5

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

The description is long but well-structured with clear headings, examples, and an args list. It front-loads the main purpose and only includes information that aids usage, though the multiple examples make it slightly verbose.

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

Completeness5/5

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

Given the tool's complexity and missing schema descriptions, the description is exceptionally complete. It covers all parameters, return value, chart type behaviors, and multi-series scenarios, making it self-sufficient for an agent to invoke correctly.

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

Parameters5/5

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

The schema has 0% description coverage, but the description includes a comprehensive 'Args' section explaining each parameter, its default, and usage context. Examples further illustrate parameter combinations, fully compensating for the schema's lack of 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 it creates an embedded chart with MULTIPLE SERIES support, using a specific verb and resource. It distinguishes itself from sibling tools like list_charts and delete_chart by being the creation operation, and the chart type explanations further clarify its unique purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides detailed examples of when to use different chart types and auto-detection behavior, giving clear context for typical usage. However, it does not explicitly mention alternatives or when not to use the tool, though its distinct purpose among siblings makes this less critical.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dudegladiator/spreadsheet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server