Skip to main content
Glama
Hermoso

Hermoso

Official

Create a Google Sheet

create_sheet

Create a new Google Spreadsheet in Drive and optionally populate it with row data, such as ad lists, swipefiles, or performance reports. Returns the spreadsheet ID and URL.

Instructions

Create a new Google Spreadsheet in the user’s Drive and optionally fill it with rows — e.g. export a swipefile, ad list, or performance report. Pass rows as an array of row arrays (first row = headers). Returns the spreadsheet id + URL. Needs Google Drive connected (Connectors > Google Drive — one connection covers Drive, Sheets and Docs).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNorows to write — array of row arrays; first row = headers
titleNospreadsheet title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.454
    • removedInput schema / properties / rows / items / items / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  }
      -]
    • addedInput schema / properties / rows / items / items / type
      Added value: +[
      +  "string",
      +  "number",
      +  "boolean"
      +]
  2. Addedv0.1.161

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, non-idempotent, open-world create; the description adds the auth prerequisite (Drive must be connected, one connection covers Drive/Sheets/Docs) and the return payload (spreadsheet id + URL), both of which the annotations cannot convey. It does not discuss duplicate-title behavior or whether an existing sheet is ever overwritten.

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?

The core action is front-loaded in the first clause, and each following segment — examples, row format, return value, prerequisite — carries distinct information. The run-on em-dash styling is dense but nothing is redundant with the tool name or annotations.

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?

For a two-parameter create tool with no output schema, the description covers the action, the data shape, the return value, and the connection prerequisite. An agent can call this correctly without opening the schema.

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 the parameter documentation burden is already met by the schema. The description restates the rows format ('array of row arrays, first row = headers') without adding structure beyond the schema and says nothing about the title parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a new Google Spreadsheet in the user's Drive') plus the optional content-fill behavior, which clearly separates it from create_doc, append_to_sheet, and the other sheet-mutating siblings.

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?

Gives concrete use cases ('export a swipefile, ad list, or performance report') and a prerequisite, so the agent knows the context in which this tool applies. It stops short of naming an alternative or an explicit when-not condition (e.g. vs. append_to_sheet for existing sheets).

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

Deploy Server

Other Tools