ShareWatch

Create Folder

create_folder

Create a folder in Google Drive. Use this to organize files. The folder can be set as the default location for new files.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Folder name
`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.
`parent_id`	No	Parent folder ID. If omitted creates in Drive root.
`set_as_default`	No	If true set this folder as the default for new ShareWatch files.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	link that opens the folder in Drive
`name`	Yes	the folder's name as Drive recorded it
`account`	No	the Google account the folder was created in; present only when more than one is connected
`folder_id`	Yes	Drive ID of the new folder — use this as parent_id or folder_id in later calls
`parent_id`	No	the folder it was created inside, absent if created at the Drive root
`is_default_folder`	Yes	true if this folder is now the default destination for new files

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 folder 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

A3.5/5.0

Behavior3/5

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

Annotations already state readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the folder can be a default location for new files, which is useful behavioral context, but it says nothing about duplicate-creation on repeated calls, permission needs, or account scoping beyond what the schema covers.

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

Conciseness4/5

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

Three short sentences, front-loaded with the core action, no padding. The third sentence is somewhat redundant with the schema's set_as_default description, which keeps it from a 5.

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 annotations carrying the safety profile and an output schema handling return values, the description only needs to establish purpose and scope, which it does. Slightly thin on interactions with sibling tools (e.g., where the created folder lands relative to move_file), but adequate for a simple 4-parameter creator.

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 (name, account, parent_id, set_as_default) with good detail. The description only echoes the set_as_default capability, adding no syntax, format, or edge-case meaning beyond the schema; baseline 3 applies.

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?

The description gives a specific verb and resource ('Create a folder in Google Drive') plus an intent ('organize files'), so an agent immediately knows what it does. It does not distinguish itself from siblings such as move_file or upload_file that also touch Drive structure, so it falls short of a 5.

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?

'Use this to organize files' implies a use case but gives no when-not conditions and names no alternatives among the many sibling tools. Usage is inferable but not explicit.

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?