Skip to main content
Glama

drive create folder

drive_create_folder

Create a new Google Drive folder by name, optionally nested under an existing parent folder. Use it to organize files programmatically through audited write access.

Instructions

Create a Drive folder. Write operation; audited.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
parent_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so "Write operation" is largely redundant. "Audited" is genuine added context not present in the structured fields, but the description says nothing about required permissions, behavior when parent_id is null (root), or duplicate-name handling.

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?

Two short, front-loaded sentences with no filler. It is efficient, though so terse that the second sentence spends words restating the annotation-declared write nature instead of adding parameter context.

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?

The output schema means return values need not be explained, and the tool is simple with two parameters. Still, for a mutating create tool the definition omits parent-folder semantics, permission requirements, and any conflict behavior, leaving key gaps for an agent to guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description mentions no parameters at all. The meaning of parent_id (default null = create at drive root, and whether the folder must be shared with the caller) is left entirely to inference from the bare schema titles.

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?

"Create a Drive folder" states a specific verb and resource, so an agent immediately knows the operation. It does not distinguish itself from siblings such as drive_upload_file or drive_move_file (which can also create nested folders implicitly), but the core purpose is unambiguous.

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: nothing says whether this is the right call versus drive_upload_file, drive_copy_file, or drive_move_file, and no prerequisites (parent must exist, name collisions) are mentioned. Usage is only implied by the verb.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.