Skip to main content
Glama
Sign In
Google Drive MCP

Google Drive MCP

by EgCooper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_folder

Create a new folder in Google Drive with a specified name, optionally within a parent folder, to organize documents.

Instructions

Crea una carpeta en Google Drive.

Args: name: Nombre de la carpeta. parent_id: Carpeta padre. Vacío = raíz.

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": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
parent_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

There are no annotations, and the description only states the action and parameter details. It adds minimal behavioral context (e.g., 'Vacío = raíz' for parent_id) but does not disclose error handling, idempotency, or return behavior.

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 sentence plus a compact args list. It is front-loaded with the main purpose and has no unnecessary words.

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?

Given the simplicity of creating a folder, the essential purpose and parameters are covered. However, the lack of behavioral details (e.g., duplicate handling, permissions) and absence of usage guidance makes it somewhat incomplete, though the output schema may fill some gaps.

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

Parameters4/5

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

The schema has zero description coverage, and the description compensates by explaining both parameters: 'name' (Nombre de la carpeta) and 'parent_id' (Carpeta padre, Vacío = raíz). This adds meaningful semantics beyond the raw schema types.

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 'Crea una carpeta en Google Drive' (creates a folder in Google Drive), which is a specific verb+resource. This distinguishes it from sibling tools that operate on files (list_files, delete_file, etc.).

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?

No guidance is provided on when to use this tool versus alternatives. For example, there is no mention of how it relates to uploading files or moving files, nor any prerequisites or exclusions.

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