Skip to main content
Glama
Sign In
Gmail Multi-Inbox MCP Server

Gmail Multi-Inbox MCP Server

by tszaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_drive_folder

Create a Google Drive folder under a specified account, optionally placing it inside a parent folder.

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": {
      "account": "<account>",
      "name": "<name>"
    },
    "name": "create_drive_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name.
accountYesAccount id.
parent_idNoOptional parent folder ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.2

TDQS

C2.9/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only repeats the tool's name ('Create a new folder') and does not mention permissions, duplicate handling, return values, side effects, or any real behavioral context. For a mutation tool, this is a substantial transparency gap.

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?

The description is a single short sentence with no wasted words, which is efficient and front-loaded. However, it is somewhat redundant with the tool name and does not include any additional structural elements like examples or context, making it concise but minimal.

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

Completeness2/5

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

Given that there are no annotations and no output schema, the description should provide more context about behavior, such as what happens if parent_id is omitted or what the response includes. The schema covers the parameters, but the tool's overall behavior remains under-specified, making this less than minimum viable.

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 has 100% description coverage for all three parameters, so the baseline is 3. The description adds no parameter-specific information, but since the schema already documents name, account, and parent_id meanings, the description need not compensate.

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 uses a specific verb 'Create' and clearly identifies the resource as 'a new folder in Google Drive,' which unambiguously distinguishes it from sibling tools like create_label or docs_create. It matches the tool name exactly and leaves no doubt about the action performed.

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?

The description provides no guidance on when to use this tool versus alternatives such as upload_drive_file or share_drive_file, nor does it mention any prerequisites like existing parent folders. There is no context about typical use cases or exclusions, leaving the agent without decision-making support.

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