Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Copy Drive File

copy_drive_file

Duplicate a Google Drive file to a new folder or with a new name while preserving original content and formatting.

Instructions

Creates a copy of an existing Google Drive file.

This tool copies the template document to a new location with an optional new name. The copy maintains all formatting and content from the original file.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`file_id`	Yes	The ID of the file to copy. Required.
`new_name`	No	New name for the copied file. If not provided, uses "Copy of [original name]".
`parent_folder_id`	No	The ID of the folder where the copy should be created. Defaults to 'root' (My Drive).	root
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / new_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / new_name / type
```
Added value: +"string"
```
Addedv1.0.1Jul 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already carry the read-only, destructive, and idempotence signals, so the description only needs to add behavioral context. It adds useful specifics: the file is copied to a new location, may be renamed, and retains all formatting and content. It does not contradict the annotations.

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 compact and front-loaded: the core action is stated in the first sentence, followed by two short sentences that expand on destination, name, and outcome. Every sentence earns its place with no filler.

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

Completeness4/5

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

Combined with the fully documented schema, the description gives enough information for a correct call: what is copied, where it goes, whether a new name can be set, and that content is preserved. It stops short of a 5 because it does not address what happens to permissions or sharing on the copied file, a common ambiguity when duplicating Drive files.

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?

Schema description coverage is 100%, so the baseline is 3. The description's references to a 'new location' and 'optional new name' loosely map to parent_folder_id and new_name, but it adds little beyond what the schema already states with defaults and descriptions.

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 opens with 'Creates a copy of an existing Google Drive file,' which names a specific action and resource. It clarifies the operation by adding that the copy goes to a new location and preserves formatting/content, making it easy to distinguish from sibling tools like create_drive_file or update_drive_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 clearly implies this tool is for duplicating existing files, but it never explicitly states when to prefer it over alternatives such as create_drive_file or import_to_google_doc. There are no exclusions or prerequisite conditions, so usage guidance remains implicit rather than explicit.

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

Deploy Server