Skip to main content
Glama
Sign In
MCP Google Multi-Account Server

MCP Google Multi-Account Server

by bkbaheti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

drive_create_folder

Create a new folder in Google Drive. Specify the Google account and optionally a parent folder to organize files.

Instructions

Create a new folder in Google Drive.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>",
      "name": "<name>"
    },
    "name": "drive_create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name
accountIdYesThe Google account ID, alias, or email
parentFolderIdNoParent folder ID (default: root)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

B3.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action and gives no details about permissions, default parent folder behavior, error handling, or return value.

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 a single, direct sentence with no superfluous information, making it well-structured and easy to parse.

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

Completeness3/5

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

The tool is simple and the schema fully covers parameters, but with no output schema and no behavioral details, the description is only minimally complete. It does not mention what happens on success or the returned folder ID.

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?

The input schema provides complete descriptions for all three parameters (name, accountId, parentFolderId), so the description adds no additional parameter semantics. The baseline of 3 applies due to high schema coverage.

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 clearly states the action ('Create') and the resource ('a new folder in Google Drive'), which is specific and distinguishes it from sibling tools like drive_rename_file or drive_upload_file.

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's use case clearly but provides no explicit guidance on when to choose this over alternatives or any exclusions. Since no sibling tool creates folders, the context is straightforward but still not fully explicit.

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