ShareWatch

Create Spreadsheet

create_spreadsheet

Create a new Google Sheet. Pass sheet_names_json to create multiple tabs at once (data_json writes to the first tab).

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Spreadsheet title
`data_json`	No	JSON-encoded 2D array of cell values written to the first tab. Example: [["Name","Age"],["Alice","30"]]
`sheet_name`	No	Name for the first sheet tab. Defaults to 'Sheet1'. Ignored if sheet_names_json is provided.
`sheet_names_json`	No	JSON-encoded array of tab names to create. Example: ["Overview","Weekly Plan","Strength Library"]. The first tab is the primary tab and receives any data_json content.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already communicate that this is a mutating, non-destructive, non-idempotent operation. The description adds useful behavioral context: passing sheet_names_json creates multiple tabs in one action, and data_json is written to the first tab. It does not contradict the 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?

Two short sentences accomplish everything: the primary purpose is front-loaded, and the optional multi-tab behavior is stated in a compact parenthetical. There is no filler or redundant repetition of the schema.

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

Completeness4/5

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

Given the output schema and fully documented parameters, the description is mostly complete: it explains the create action and the important multi-tab/data-placement behavior. It is only slightly incomplete in not guiding the agent toward add_sheet_tab or update_spreadsheet for follow-up operations on existing sheets.

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%, so the schema already documents all four parameters. The description adds a brief cross-parameter relationship between sheet_names_json and data_json, but this is largely already present in the schema 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 states a specific verb and resource: 'Create a new Google Sheet.' This clearly distinguishes it from sibling tools like create_document and create_presentation, and from update_spreadsheet for modifications.

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?

The description implies the tool is for creating new sheets and suggests using sheet_names_json for multi-tab creation, but it never explicitly contrasts with siblings like add_sheet_tab for existing sheets or update_spreadsheet for later edits. No exclusions or alternative-selection conditions are named.

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

All ShareWatch tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools target a distinct resource and action, and the detailed descriptions separate similar-sounding ones. A few pairs could still be confused: access_file_by_url vs request_file_access, and create_document vs format_document, but their trigger conditions are described clearly enough to avoid frequent misselection.

Naming Consistency4/5

The set mostly follows a verb_noun pattern with consistent snake_case, e.g. create_document, update_spreadsheet, delete_file. Minor deviations like build_presentation instead of create_presentation, and format_document alongside create_document, break the pattern slightly but remain readable and predictable.

Tool Count3/5

25 tools is at the heavy end of the scale, though the domain spans Drive, Docs, Sheets, and Slides, which justifies a large surface. Some consolidation is possible — access_file_by_url and request_file_access overlap, as do create_document and format_document — so the count feels slightly bloated rather than tightly scoped.

Completeness4/5

The server covers the core file lifecycle well: create, read, update, delete, move, list, search, upload, and access control across all major Google Workspace document types. Minor gaps exist, such as no rename, copy, export, or direct sharing tool, but agents can work around these without major failures.

Resources

Need Help?