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
`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
`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. Dates show when Glama detected each change.

First observedSep 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructiveness (destructiveHint=false). The description adds the notable side effect that the folder 'can be set as the default location for new files,' which is meaningful behavioral context beyond the annotations. It does not discuss duplicate-name behavior or permissions, but these are secondary for this simple creation tool.

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 description is three short sentences with no filler. It front-loads the core action, states the primary purpose, and then provides the useful default-location caveat. Every sentence earns its place.

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?

For a simple three-parameter creation tool with an output schema, complete parameter documentation, and safety-relevant annotations, the description covers what an agent needs to select and invoke it correctly. It could add caveats about duplicate names or permissions, but these are not critical given the schema and annotation coverage.

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%: name, parent_id, and set_as_default all have their own descriptions, including the root-folder behavior for parent_id. The free-text description only restates the set_as_default concept at a high level and does not add meaningful parameter detail beyond the schema. 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?

The description states a specific action and object: 'Create a folder in Google Drive.' This clearly distinguishes it from sibling creation tools like create_document or create_spreadsheet. The added purpose 'Use this to organize files' reinforces what the tool is for.

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?

The description explicitly says 'Use this to organize files,' giving a clear use case. It does not name alternatives or exclusions, but the folder-vs-file distinction among sibling tools makes the appropriate context reasonably evident. This is clear guidance without formal when-not-to-use conditions.

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?