Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

Create Google Spreadsheet

sheets_create_spreadsheet

Create a Google Spreadsheet by providing a title and optional sheet names, then retrieve its ID, URL, and sheet details.

Instructions

Create a new Google Spreadsheet with optional sheet names.

Args:

  • title (string): The title for the new spreadsheet

  • sheet_titles (string[], optional): Array of sheet names to create

Returns: { "spreadsheetId": string, "title": string, "spreadsheetUrl": string, "sheets": [{ "sheetId": number, "title": string }] }

Examples:

  • Create basic: title="My Spreadsheet"

  • With sheets: title="Budget", sheet_titles=["Income", "Expenses", "Summary"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe title for the new spreadsheet
sheet_titlesNoOptional array of sheet names to create (default: one sheet named 'Sheet1')
Behavior4/5

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

Annotations already indicate non-readonly, non-destructive, non-idempotent, open-world. Description adds return format details and default sheet name behavior, providing useful behavioral context beyond annotations.

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?

Description is structured with Args, Returns, and Examples in a compact format. Every sentence is informative, no fluff, and the most important info (purpose) is front-loaded.

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 no output schema, description provides complete return type. Two simple parameters are fully described with examples. Context is sufficient for an agent to understand and invoke the tool correctly.

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 coverage is 100%, so baseline is 3. Description restates schema info for title and sheet_titles but adds examples showing how parameters are used, which adds some meaning but doesn't significantly exceed schema.

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?

Description clearly states 'Create a new Google Spreadsheet with optional sheet names.' Specific verb 'create', resource 'Google Spreadsheet', and optional sheet names differentiate it from sibling tools like sheets_get_spreadsheet or sheets_update_values.

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

Usage Guidelines3/5

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

Examples show common usage patterns (basic and with sheets) but no explicit when-to-use or when-not-to-use compared to alternatives like sheets_batch_update. Usage is implied but not fully guided.

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/EveryInc/google-workspace-mcp-server'

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