Skip to main content
Glama
shakhin85

Google Sheets MCP Server

by shakhin85

merge_cells

Merges a range of cells in a Google Sheet, with options to merge all, merge columns, or merge rows.

Instructions

Merge cells in a range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_rowYesEnding row index (exclusive)
sheet_idYesThe ID of the sheet
start_rowYesStarting row index (0-based)
end_columnYesEnding column index (exclusive)
merge_typeYesHow to merge the cells
start_columnYesStarting column index (0-based)
spreadsheet_idYesThe ID of the spreadsheet
Behavior1/5

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

No annotations provided, so description must fully disclose behavior. It only states 'merge cells' without explaining effects (e.g., data loss, formatting changes, or that merging is a mutation). This is a severe gap.

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

Conciseness2/5

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

Extremely short but at the expense of necessary information. Not a case of conciseness but of under-specification.

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?

Given 7 required parameters and no output schema, the description fails to explain return behavior, effects of merging, or any side effects. Highly incomplete for an agent to use correctly.

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

Parameters2/5

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

Schema has 100% coverage with descriptions for all 7 parameters, but the tool description adds no additional meaning or context to the parameters. It does not summarize or clarify beyond what the schema already provides.

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?

Description clearly states the action (merge) and resource (cells in a range). It is specific enough to understand the basic function, though lacks details on behavior. Distinguishes from sibling 'unmerge_cells' by name.

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 vs alternatives like unmerge_cells. No prerequisites or context provided.

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/shakhin85/google-sheets-mcp-server'

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