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
`account`	No	Which connected Google account to create in, by its address, when the user has more than one — see get_status connections. Omit for the primary account.
`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
`id`	Yes
`url`	Yes
`account`	No	the Google account the file was created in; present only when more than one is connected

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 11, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "Which connected Google account to create in, by its address, when the user has more than one — see get_status connections. Omit for the primary account.",
+  "type": "string"
+}

addedOutput schema / properties / account

Added value: +{
+  "description": "the Google account the file was created in; present only when more than one is connected",
+  "type": "string"
+}

Changed1 schema field changedSep 10, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
First observedSep 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutation profile is covered. The description adds genuinely useful cross-parameter behavior: sheet_names_json creates multiple tabs and data_json targets the first tab. It omits any account/auth or side-effect context beyond that, so a mid-range score is appropriate.

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, front-loaded with the core action and followed immediately by the key cross-parameter constraint. No filler or restated boilerplate.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. The description covers the essential tab/data interaction, though it is silent on account selection and any failure modes for a 5-parameter mutation tool.

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 baseline is 3. The description reinforces how data_json and sheet_names_json interact (data_json writes to the first tab), which is also stated in the schema, but adds no syntax or format guidance beyond it.

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?

Opening sentence gives a specific verb and resource ('Create a new Google Sheet'), which distinguishes it from siblings like create_document and create_presentation. However, it never explicitly names an alternative or clarifies scope beyond the resource type.

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?

There is no when-to-use guidance or when-not-to-use guidance. The second sentence describes parameter behavior (multi-tab creation), not usage context, so an agent gets no help deciding between this and create_document or upload_file.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?