Skip to main content
Glama
Sign In
Google Drive MCP

Google Drive MCP

by EgCooper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_file

Move a file or folder to a different folder in Google Drive by specifying the file ID and the destination folder ID.

Instructions

Mueve un archivo o carpeta a otra carpeta.

Args: file_id: ID del archivo o carpeta a mover. folder_id: ID de la carpeta destino.

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": {
      "file_id": "<file_id>",
      "folder_id": "<folder_id>"
    },
    "name": "move_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
folder_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action and does not mention side effects (e.g., original removed, overwrite behavior), permission requirements, or failure conditions. This is a significant gap for a mutation operation.

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 extremely concise, with a clear single-sentence purpose followed by a compact Args list. Every word adds value, with no redundant or filler content. The structure is easy to parse and front-loads the main action.

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 with two well-documented parameters and an output schema exists, so return values are not needed. However, the absence of behavioral context—such as whether the move overwrites, requires special permissions, or permanently deletes the source—leaves the description incomplete for an agent to fully anticipate consequences.

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 description explicitly explains both parameters: file_id as the ID of the file/folder to move, and folder_id as the ID of the destination folder. This adds meaningful context beyond the bare schema types and required flags, compensating for the 0% schema description 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 uses a specific verb ('Mueve' = moves) and clearly identifies the resource (file or folder) and destination (another folder). It uniquely distinguishes this tool from siblings like delete_file or upload_text_file, all of which perform different operations.

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 usage for relocating files or folders, but offers no explicit guidance on when to use this versus alternatives, nor any exclusions or prerequisites. It is not misleading, but the context is minimal.

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